Description
I’m syncing upcoming meetings using the list meetings API, and subscribing to the meeting.started webhook so I can start recording. But the uuid that comes back in the webhook doesn’t match the uuid I previously got using the API. Are they not expected to be the same?
If these two uuids are not expected to match, how can I reliably match the webhook with the meeting that I previously synced? If I understand correctly, the meeting id is not guaranteed to be unique.
Hi @sunilp
Thanks for reaching out to us.
When a meeting is created, a unique meeting ID and UUID will be associated with it. And when you start that meeting for the first time, the meeting UUID that you receive from your webhook, will be the same.
If you happen to start that meeting again, then a new meeting UUID will be generated for the new instance of that meeting.
Here is a helpful blog post about meetings UUID and IDs
Meeting IDs are unique, so you can rely on meeting ID to match the webhook and the API call.
This doesn’t match what I’m seeing, at least not in the case when the meeting was created using PMI.
In my case, the meetings are being created separately, and I’m using the List Meetings API to see what meetings have been created for a particular user. I just scheduled a meeting, and I see this returned in the List Meetings API:
As far as I can tell, this uuid corresponds to the PMI, because if there are multiple meetings scheduled with PMI, calling Get Meeting on any of them returns the same uuid.
Now when I start the meeting, the meeting.started webhook will have the uuid 3+wE3dqpSbSQDH0MTm0rug== and meeting id 8434094380. The webhook payload does not contain the original uuid rZQw5pznR5KpgXTl6qGQJQ== or meeting id 83474338371 or topic or anything that will let me tie it back to the original meeting.
It would be nice if webhook contained the original meeting id or the uuid.