set Zoom Meeting using Utility - HTTP

[sumire]

Hello,

I want to set up a Zoom meeting using "Utility - HTTP".
First, I created a "Server-to-Server OAuth" app in the Zoom Marketplace.
Then I created a VBO to get Token using client id and client secret. 
This worked and I was able to get the Token.
However, I cannot use this Token to set up a Zoom meeting.
It returns "400 Bad Request".

In the same environment, I was able to set up a meeting in Python using this application.

Below is a screenshot of the "Post JSON" action of the "Utility - HTTP" VBO.

JSON is:

{
    "topic": "SampleMeeting",
    "start_time": "2024-01-06T13:00:00",
    "duration": 60,
    "timezone": "Asia/Tokyo",
}

Please advise me where to find the cause of the problem.

Thanks for your help,

------------------------------
Mitsuko
Asia/Tokyo
------------------------------

[LeonardoSQueiroz]

Hello,

Check that the , in the "," syntax at the end of the json cannot be impacting.

Try this and see if it works.

{

     "topic": "SampleMeeting",

     "start_time": "2024-01-06T13:00:00",

     "duration": 60,

     "timezone": "Asia/Tokyo"

}

Regards,

------------------------------
Leonardo Soares
RPA Developer Tech Leader
Bridge Consulting
América/Brazil
------------------------------

[sumire]

Hello @LeonardoSQueiroz,

Thank you, it worked, so I could create a VBO.

But it don't work if it is nested:

{
     "topic": "SampleMeeting",
     "start_time": "2024-01-06T13:00:00",
     "duration": 60,
     "timezone": "Asia/Tokyo",
     "settings": {
          "host_video", True
     }
}

What is wrong with the nested structure I wrote?

------------------------------
Mitsuko
Asia/Tokyo
------------------------------

[kirtimaantalwar]

Hi Mitsuko,

In the provided JSON, there's a syntax error in the "settings" section. The colon (":") should be used instead of a comma (",") for specifying key-value pairs within the "settings" object. 

Try using the below JSON. 

{

     "topic": "SampleMeeting",

     "start_time": "2024-01-06T13:00:00",

     "duration": 60,

     "timezone": "Asia/Tokyo",

     "settings": {

          "host_video": true

     }

}

I hope it will resolve the issue. 

------------------------------
KirtiMaan Talwar
IA Consultant
Deloitte USI
------------------------------