Is there any specific meetingUUID format

[Sanu]

Hi everyone,
@elisa.zoom @expertswho
I’m working on integrating Zoom’s API into my project and need some clarity on the format and validation of meeting UUIDs. Specifically, I have a few questions:

1. Format: Is there a specific format for the meeting UUID? Does it always end with “==”?
2. Length: Does the meeting UUID have a fixed number of characters?
3. Validation: How can I validate a meeting UUID string?
4. Characters Used: What characters are used to form the meeting UUID?

From my research, here’s what I’ve gathered so far:

• Base64 Encoding: Zoom meeting UUIDs are typically base64 encoded, which often results in strings that end with “==” due to padding.
• Variable Length: The length of the UUID can vary, but it is commonly around 22 characters when base64 encoded.
• Special Characters: The UUID can contain characters like “/”, which may require double encoding when used in API requests.

Sample UUIDs:

• abcd1234efgh5678ijkl==
• mnopqrstu/vwxyz==
• 1234567890abcdefg==

[expertswho (John Drinkwater MVP)]

hi @Sanu ,

I have not seen a fixed definition of a UUID,
I would not want for there to be such as people who have tried to zoombomb and
other actions by guessing the meeting ID would have another target.

But you are correct that it uses an encoding algorithm. So expect any alphahumber and special characters and an encoded string.

All the best

John