The relationship between the
id returned in the Create Meeting API operation, the “joinable” meeting id (found within
join_url) is inconsistent when related to the Personal Meeting ID (PMI) setting.
“Invalid meeting id” when trying to join meeting by id
Which App Type (OAuth / Chatbot / JWT / Webhook)?
How To Reproduce (If applicable)
Steps to reproduce the behavior:
- Set “Use Personal Meeting ID (PMI) when scheduling a meeting” setting to True
- POST to create a meeting without passing in the
use_pmiparam (default False according to docs)
- Compare the
idreturned in the response with the id included in the
join_urlin the response. The
idwill be a typical 9xxxxxxx id, but the id in the
join_urlwill be the PMI.
This caused unexpected behavior in our clients trying to join the meeting by id. If we used the 9xxxx
id in the response, we would get a “meeting does not exist” error.
Expected behavior: the meeting id returned in the API response is a valid meeting id.
If the expected behavior is actually “wrong,” I think this should be documented somewhere because it was unexpected to us and was a tricky bug to track down the cause.
Would also appreciate if the API docs explicitly stated that even though the
use_pmi field defaults to False, if the user-level “Use Personal Meeting ID (PMI) when scheduling a meeting” overrides the setting. You must explicitly pass
use_pmi: False if you want to override this user setting.