Some meetings (Type:3) are missing start_time

API and Webhooks Meetings
1

API Endpoint(s) and/or Zoom API Event(s)
GET /users/{userId}/meetings

Description
I am finding that when getting the list of meetings some meetings of type 3 (recurring) do not have a value for start_time while others do. As I understand it, type 3 meetings should always have a start_time.

Is this expected?
If so how does this occur for the user?

eg. meeting w/ uuid XC3hFhc+QNyPZJ/Yoz8CZQ== below from my current response to GET https://api.zoom.us/v2/users/me/meetings yields the following (note, this is a subset of the full result):

"meetings": [
        {
            "uuid": "XC3hFhc+QNyPZJ/Yoz8CZQ==",
            "id": 97841502262,
            "host_id": "GSFrfGtzTWyD8MnWIwJ0qQ",
            "topic": "Weekly Tapestry Dev Sync",
            "type": 3,
            "duration": 30,
            "timezone": "America/Chicago",
            "created_at": "2022-11-16T23:01:36Z",
            "join_url": "redacted"
        },
        ...
        {
            "uuid": "h4VjZW98QIOrmb+UqZRk2w==",
            "id": 99089424329,
            "host_id": "GSFrfGtzTWyD8MnWIwJ0qQ",
            "topic": "Eileen:G - Connect",
            "type": 3,
            "start_time": "2022-11-30T02:00:00Z",
            "duration": 30,
            "timezone": "America/Chicago",
            "created_at": "2022-11-30T01:32:49Z",
            "join_url": "redacted"
        },
        ...
2

Hi @gibron
Thanks for reaching out to us!
This is interesting.
Allow me some time to do some testing on my end and to look into these meeting IDs you have shared and will get back to you with an update.
Cheers,
Elisa

3

Thanks @elisa.zoom!

Any luck so far?

Happy to test more on my end if helpful.

4

Hi @gibron
I apologize for the late reply here!
I just looked into this meeting UUID XC3hFhc+QNyPZJ/Yoz8CZQ==
and It looks like it got started recently, could you please try and call the endpoint again and see if you are still getting the same response?
The first thing that came to my mind when looking into this was that probably those meeting instances where never used/started and that is why you are getting no start_time on the response.
Please, run the same request and let me know if you are still seeing this.
Cheers,
Elisa

5

Hi @elisa.zoom, appreciate you taking a look!

I ran it again and I’m getting the same results:

            "uuid": "iBvi0VqFTUW84P/CQA8Xpg==",
            "id": 97841502262,
            "host_id": "GSFrfGtzTWyD8MnWIwJ0qQ",
            "topic": "Weekly Tapestry Dev Sync",
            "type": 3,
            "duration": 30,
            "timezone": "America/Chicago",
            "created_at": "2022-11-16T23:01:36Z",
            "join_url": "redacted"
        },

It’s a recurring meeting (type 3). It has been used almost every Monday for awhile. The odd part is that there are other recurring meetings in the response that do have a start_time.

It feels like a bug in the response. There have been other instances of it as well that we have had users generate. We have code that depend on the start_time being present and I am trying to figure out if this is a durable part of the response. It feels like it should be based on the API documentation.

6

Interesting.
If you query meetings type 3, it is expected to not get a start time, because the type 3 meetings are recurring meetings with no fixed time. But what is making this interesting is that for some of these you are getting a start_time

I am going to send you a Private Message, please follow up there so I can take a closer look
Cheers,
Elisa