Unexpected Behavior with PMIs and Create Meeting API

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)?

Which Endpoint/s?

How To Reproduce (If applicable)
Steps to reproduce the behavior:

  1. Set “Use Personal Meeting ID (PMI) when scheduling a meeting” setting to True
  2. POST to create a meeting without passing in the use_pmi param (default False according to docs)
  3. Compare the id returned in the response with the id included in the join_url in the response. The id will be a typical 9xxxxxxx id, but the id in the join_url will 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.

Additional context
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.

Hey @ssnow,

This is actually expected behavior, checkout my post here for more details: