When we create a meeting using create meeting API it return two type of ids in response i.e “uuid”: “unique_id”, “id”: “123456789”. While fetching meeting by Id we need to pass meeting id for get meeting api call, so if I pass value received as “uuid” it gives error but if I pass value received in “id” it works fine. But document is bit confusing, as it says to pass “unique_id” not the “123456789”. Please have a look.
“ID” vs “UUID” vs “Unique ID” vs “Meeting ID” are used in different places in the documentation, which is confusing when planning out a series of calls.
@joshua, I’ve been writing against this api and it’s the uuid that needs to get passed, not the meeting id. This makes sense as meeting id’s are recycled, no?
upddate: Just looked at the docs again. It looks like the description has been updated, but I would change meeting_id to uuid and updadte the referenced curl example on the far right
