# Unexpected Behavior with PMIs and Create Meeting API

**URL:** <https://devforum.zoom.us/t/unexpected-behavior-with-pmis-and-create-meeting-api/21639>\
**Category:** API and Webhooks\
**Created:** [June 17, 2020, 6:41pm UTC](https://devforum.zoom.us/t/unexpected-behavior-with-pmis-and-create-meeting-api/21639 "2020-06-17T18:41:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ssnow](https://avatars.discourse-cdn.com/v4/letter/s/5f8ce5/32.png) [@ssnow](https://devforum.zoom.us/u/ssnow)\
**Post date:** [June 17, 2020, 6:41pm UTC](https://devforum.zoom.us/t/unexpected-behavior-with-pmis-and-create-meeting-api/21639/1 "2020-06-17T18:41:28Z")

</div>

**Description**  
The relationship between the `id` returned in the [Create Meeting](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate) API operation, the “joinable” meeting id (found within `join_url`) is inconsistent when related to the Personal Meeting ID (PMI) setting.

**Error**  
“Invalid meeting id” when trying to join meeting by id

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

**Which Endpoint/s?**

> **[Create a Meeting - Meetings - Zoom API - API Reference](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate)**
>
> Create a meeting for a user. This API has a daily rate limit of 100 requests per day. Therefore, only 100 Create a Meeting API requests are permitted wi...

**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.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [June 19, 2020, 9:57pm UTC](https://devforum.zoom.us/t/unexpected-behavior-with-pmis-and-create-meeting-api/21639/2 "2020-06-19T21:57:40Z")

</div>

Hey @ssnow,

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

> [@Understanding scheduled PMI meetings](https://devforum.zoom.us/t/understanding-scheduled-pmi-meetings/15406/2):
>
> Hey @jimig, Correct, but you should be able to pass in your PMI to the endpoints and get the respective data. This is actually the expected flow. When a meeting is created using personal meeting ID, a unique meeting ID is also created as seen in the create meeting response. However, in the webhooks it will show your personal meeting ID. Basically since you can have infinite meetings with your personal meeting ID, we also assign a unique meetingID to handle in our system. Here is an example…

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 10:09pm UTC](https://devforum.zoom.us/t/unexpected-behavior-with-pmis-and-create-meeting-api/21639/3 "2020-08-21T22:09:54Z")

</div>

Closed on August 21, 2020, 10:09pm UTC


