Create meeting API meeting ID inconsistencies

Sometimes (we aren’t able to determine when this happens), when creating a meeting using the API with only the default “settings”, the information in the response does not match the information in the UI. The returned “ID” in the response is a newly generated number, but the join_url in the response has the user’s PMI (despite leaving settings.use_pmi as the default (false)). In the UI, both the join_url and the ID are the user’s PMI. This is confusing our users. This does not happen always, but only sometimes.


  1. Meeting created with PMI instead of new ID
  2. “ID” in API response does not match ID in Zoom website (on website the ID displayed is the PMI)
  3. “ID” in API response does not match “join_url” in API reponse.

Which App Type (OAuth / Chatbot / JWT / Webhook)?

Which Endpoint/s?


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

  1. POST to create a meeting using the default “settings”
  2. Check response. Is id different than the number in join_url? Is the meeting code in the code the user’s PMI?

Screenshots (If applicable)

Additional context

Hi @danielb,

Happy to help you.

All the scheduled meetings with a PMI will have a real meeting ID. The participants can use PMI to join this meeting. So the join URL or the meeting ID provided to the participants can be PMI instead of the real meeting ID. But they can also use the real meeting ID to join this meeting.

Let me know if this helps.


1 Like