# 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:** 1\
**Showing post:** 2

<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

---

_[View the full topic](https://devforum.zoom.us/t/unexpected-behavior-with-pmis-and-create-meeting-api/21639)._
