Get a meeting API returns same instance id/uuid for different meetings

Description
For a specific user the endpoint /users/{userId}/meetings?type=scheduled returns six meetings, each with different uuid as expected. For this user /meetings/{meetingId} unexpectedly returns the same uuid for all meetings.

Error
Uuid is not unique accross meetings of at least this single user. No error message obviously.

Which App Type (OAuth / Chatbot / JWT / Webhook)?
JWT

Which Endpoint/s?
Valid data: /users/{userId}/meetings
Invalid data: /meetings/{meetingId}

Additional context
Affected meeting ids: [REDACTED] (all of the same user)
Dont know of this behavior for other users.

Hey @ringwelt,

Thank you for reaching out to the Zoom Developer Forum. When using the List Meetings API, a list of the latest meetings will be returned. This will include multiple occurrences of a recurring meeting.

However, when using the Get a Meeting API, only the latest instance of the Meeting ID will be returned. In order to obtain information about a separate occurrence you can use occurrence_id field:

Let me know if that helps. :slightly_smiling_face:

Thanks,
Max

Hi Max,

this has nothing to do with occurrences/recurring meetings. The user has six meetings each of type Scheduled. See the examples below (values are random):

GET /users/{userId}/meetings

{
  "meetings": [
    {
      "id": 98765432111,
      "topic": "Meeting 11",
      "type": 2,
      [...],
      "uuid": "u6f4HIsER3MNhe=="
    },
    {
      "id": 98765432122,
      "topic": "Meeting 22",
      "type": 2,
      [...],
      "uuid": "jf3g99GdsfsdHdQ=="
    },
    {
      "id": 98765432133,
      "topic": "Meeting 33",
      "type": 2,
      [...],
      "uuid": "jkf46Sdgherw3=="
    },
    {
      "id": 98765432144,
      "topic": "Meeting 44",
      "type": 2,
      [...],
      "uuid": "jsj46bdFF7Kjhje=="
    },
    {
      "id": 98765432155,
      "topic": "Meeting 55",
      "type": 2,
      [...],
      "uuid": "hskJGH43kjsdgg=="
    },
    {
      "id": 98765432166,
      "topic": "Meeting 66",
      "type": 2,
      [...],
      "uuid": "H544dKKH65fdfuI=="
    }
  ],
  "next_page_token": "",
  "page_size": 300,
  "total_records": 6
}

Now i make a request for each of the above meetings. The uuid is now always the value of the first meeting. Meetings of other users don’t show this behavior, they all return the correct uuid.

GET /meetings/98765432111

{
  "id": 98765432111,
  [...]
  "topic": "Meeting 11",
  "type": 2,
  "uuid": "u6f4HIsER3MNhe==" // Valid
}

GET /meetings/98765432122

{
  "id": 98765432122,
  [...]
  "topic": "Meeting 22",
  "type": 2,
  "uuid": "u6f4HIsER3MNhe==" // Invalid, should be jf3g99GdsfsdHdQ==
}

GET /meetings/98765432133

{
  "id": 98765432133,
  [...]
  "topic": "Meeting 33",
  "type": 2,
  "uuid": "u6f4HIsER3MNhe==" // Invalid, should be jkf46Sdgherw3==
}

GET /meetings/98765432144

{
  "id": 98765432144,
  [...]
  "topic": "Meeting 44",
  "type": 2,
  "uuid": "u6f4HIsER3MNhe==" // Invalid, should be jsj46bdFF7Kjhje==
}

GET /meetings/98765432155

{
  "id": 98765432155,
  [...]
  "topic": "Meeting 55",
  "type": 2,
  "uuid": "u6f4HIsER3MNhe==" // Invalid, should be hskJGH43kjsdgg==
}

GET /meetings/98765432166

{
  "id": 98765432166,
  [...]
  "topic": "Meeting 66",
  "type": 2,
  "uuid": "u6f4HIsER3MNhe==" // Invalid, should be H544dKKH65fdfuI==
}

Hey @ringwelt,

Thank you for providing detailed information, that helped me to understand the issue here. I tested this on my end with Postman but I didn’t see the same behavior. What are you using to make these API requests? Do you see the same behavior when testing with a REST client like Postman?

Thanks,
Max

Hi Max,

we are using the standard .NET System.Net.HttpWebRequest class, but I verified the returned invalid values via the “Send a Test Request” section in your API reference pages:

Note, this only appears for the meetings of a single user account. Can send you the corresponding user/meeting ids somehow?

Hey @ringwelt,

Thank you for clarifying. Please send an email to developersupport@zoom.us with a link to this thread. In that email, you can include Meeting IDs and any other relevant details.

I’ll be sure to investigate the issue further from there.

Thanks,
Max

Hi Max,

thank you, email has been sent out.

Thanks, @ringwelt. Our team will be in touch with you there shortly.