Create meeting endpoint problems

API and Webhooks
1

using this endpoint: v2/users/me/meetings

I want a reoccurring meeting at 1200 hours PST. I pass in a payload using the equivalent UTC ISO time string:

{
  topic: 'Meeting name',
  type: 8,
  start_time: '2025-06-21T19:00:00.000Z',
  duration: 30,
  recurrence: {
    type: 2,
    repeat_interval: 1,
    weekly_days: '7',
    end_date_time: '2025-07-12T19:00:00.000Z'
  },
  settings: { join_before_host: true, waiting_room: true, audio: 'both' }
}

I get back a result and the occurrences show that the API ignored the “Z” on the timestring, and treated my time string as a PST value instead of a UTC value. I don’t know how the API knew I am located in PST.

2

My suggestion would be to specify dates and times in your desired timezone (PST in your scenario) and also specify the name of the time zone in your payload. This way there is no need for you to convert your date/time to UTC and no need for the ‘Z’ in your date format.

It should look something like this:

    start_time: '2025-06-21T12:00:00',
    timezone: 'America/Los_Angeles',

In case you are curious, here’s the full list of time zones supported by the Zoom API.

One final detail I want to point out: as far as I l know, the Zoom API doesn’t support milliseconds, therefore no need to include ‘.000’ when specifying time.

Let me know if this helps

3

@Christopher3 To expand on what I said in my previous comment, I ran a quick test where I created a new meeting scheduled for July 22 at 1:50pm west coast time. To do that, I included the following two JSON nodes in my request:

start_time=2025-07-22T13:50:25
timezone=America/Los_Angeles

Notice the time is expressed in west coast and also notice the absence of ‘Z’ in my format.

The meeting was successfully created and the response from the Zoom API included the following two nodes in the JSON payload:

start_time=2025-07-22T20:50:25Z
timezone=America/Los_Angeles

Notice that Zoom respects the time zone I specified and notice that the date/time format has been converted to UTC but it’s important to keep in mind that the value expressed in UTC is exactly the same as the PST value I specified in my request (indeed 8:50 pm in UTC is the same point-in-time as 1:50 pm PST).

4

One other thing: I previously mentioned that I didn’t think the Zoom API supported milliseconds. Turns out: not only is it not supported, it also appears that specifying milliseconds causes the API to misinterpret date/times as mentioned here.

So the root of the issue you are experiencing is probably that you included milliseconds in your request. Removing the milliseconds probably will resolve the problem you are experiencing.

1 Like
5

hi jericho. thanks for the very thorough help here. it worked out, thank you

1 Like
6

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.