Steps to reproduce:
1.
Request URL: POST https://api.zoom.us/v2/users/{userId}/meetings
Headers: Authorization: Bearer Token
Body:
{
“agenda”:“agenda”,
“topic”:“Meeting with PMI”,
“type”:2,
“start_time”:“2022-10-10T00:00:00Z”,
“duration”:60,
“settings”:{
“use_pmi”:true,
“waiting_room”:false
}
}
We use this API Zoom Meeting API
2.
Response contains correct id (unique meetingId):
{
“uuid”: “pj/mlZfoQuOuNIkirNRcpA==”,
“id”: 81004485764,
“host_id”: HOST_ID,
“host_email”: “skydanmykola1987@gmail.com”,
“topic”: “Meeting with PMI”,
“type”: 2,
“status”: “waiting”,
“start_time”: “2022-10-10T00:00:00Z”,
“duration”: 60,
…
}
But in incoming webhook event meeting.created id is Personal Meeting Id:
{
“event”: “meeting.created”,
“payload”: {
“account_id”: ACCOUNT_ID,
“operator”: “skydanmykola1987@gmail.com”,
“operator_id”: PERSONAL_ACCOUNT_ID,
“object”: {
“uuid”: “pj/mlZfoQuOuNIkirNRcpA==”,
“id”: 5974362818,
“host_id”: PERSONAL_ACCOUNT_ID,
“topic”: “Meeting with PMI”,
“type”: 2,
“start_time”: “2022-10-10T00:00:00Z”,
“duration”: 60,
“timezone”: “Europe/Kiev”,
“join_url”: JOIN_URL,
“password”: PASSWORD,
“pmi”: “5974362818”,
“settings”: {
“use_pmi”: true,
“alternative_hosts”: “”
}
}
},
“event_ts”: 1663327646659
}
Hi @skydanmykola1987
Thanks for reaching out to the Zoom Developer Forum and welcome to our community!
I am happy to help here!
I believe this is the expected behavior, when scheduling a meeting with PMI it is expected that the meeting ID will be the one of your PMR
Allow me to do some testing on my end and I will share my findings soon.
Best,
Elisa
Hi, @elisa.zoom
Thanks for your reply!
When I create meeting with PMI directly from my Zoom account, incoming webhook event meeting.created has correct id (unique meetingId).
{
“event”: “meeting.created”,
“payload”: {
“account_id”: ACCOUNT_ID,
“operator”: “skydanmykola1987@gmail.com”,
“operator_id”: PERSONAL_ACCOUNT_ID,
“object”: {
“uuid”: “TRUMndkiRDeo4PSRodfXgQ==”,
“id”: 84073844338,
“host_id”: PERSONAL_ACCOUNT_ID,
“topic”: “Meeting With Pmi From Account”,
“type”: 2,
“start_time”: “2022-09-17T08:00:00Z”,
“duration”: 60,
“timezone”: “Europe/Kiev”,
“join_url”: JOIN_URL,
“password”: PASSWORD,
“pmi”: “5974362818”,
“settings”: {
“use_pmi”: true,
“alternative_hosts”: “”
}
}
},
“event_ts”: 1663400131761
}
But if meeting with PMI is created via API, id of this meeting in meeting.created webhook event is always PMI, but not unique meetingId. Is this really expected behavior?
Thanks in advance
Hi @skydanmykola1987
Thanks for sharing more details about this issue with me.
Could you please share the request body that you are sending when creating the meeting via API
So I can try and replicate this behavior?
Thanks
Elisa
Hi, @elisa.zoom
Yes, of course, let me share all details about creation scheduled meeting with PMI via API
Request URL: POST https://api.zoom.us/v2/users/{userId}/meetings
Headers:
Authorization: Bearer Token
Content-Type: application/json
Body:
{
“agenda”:“some agenda”,
“topic”:“Another Meeting with Personal Meeting Id via API”,
“type”:2,
“start_time”:“2022-11-11T00:00:00Z”,
“duration”:30,
“settings”:{
“use_pmi”:true,
“waiting_room”:false
}
}
Response
{
“uuid”: “pj/mlZfoQuOuNIkirNRcpA==”,
“id”: 82469456339,
“host_id”: “3DXHVsaISzSL9KQV0MKutQ”,
“host_email”: “skydanmykola1987@gmail.com”,
“topic”: “Another Meeting with Personal Meeting Id via API”,
“type”: 2,
“status”: “waiting”,
“start_time”: “2022-11-11T00:00:00Z”,
“duration”: 30,
“timezone”: “Europe/Kiev”,
“agenda”: “some agenda”,
“created_at”: “2022-09-20T07:05:42Z”,
…
}
meeting.created webhook event
{
“event”: “meeting.created”,
“payload”: {
“account_id”: ACCOUNT_ID,
“operator”: “skydanmykola1987@gmail.com”,
“operator_id”: PERSONAL_ACCOUNT_ID,
“object”: {
“uuid”: “pj/mlZfoQuOuNIkirNRcpA==”,
“id”: 5974362818,
“host_id”: PERSONAL_ACCOUNT_ID,
“topic”: “Another Meeting with Personal Meeting Id via API”,
“type”: 2,
“start_time”: “2022-11-11T00:00:00Z”,
“duration”: 30,
“timezone”: “Europe/Kiev”,
“join_url”: JOIN_URL,
“password”: PASSWORD,
“pmi”: “5974362818”,
“settings”: {
“use_pmi”: true,
“alternative_hosts”: “”
}
}
},
“event_ts”: 1663657543664
}
Hi @skydanmykola1987
Thank you so much for sharing more details with me. I did some testing on my end and I was able to replicate this behavior.
I will do some research internally to see if this is expected behavvior
Thanks a lot
Elisa
Hi @skydanmykola1987
Thank you so much for your patience and for noticing this and bringing this to our attention.
I was able to replicate this issue and created an internal ticket with our Engineering team and they are aware of this issue.
This is not the expected behavior and we are going to treat this as a bug and we will fix it on our end.
The behavior of the API and web portal should be the same.
Thanks a lot,
Elisa
Thank you and I will keep an eye on the progress of this issue and will update you accordingly! @skydanmykola1987