# Response duplicate meeting id while using Zoom API

**URL:** <https://devforum.zoom.us/t/response-duplicate-meeting-id-while-using-zoom-api/116380>\
**Category:** API and Webhooks\
**Created:** [August 26, 2024, 9:06am UTC](https://devforum.zoom.us/t/response-duplicate-meeting-id-while-using-zoom-api/116380 "2024-08-26T09:06:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![secure](https://avatars.discourse-cdn.com/v4/letter/s/edb3f5/32.png) [@secure](https://devforum.zoom.us/u/secure)\
**Post date:** [August 26, 2024, 9:06am UTC](https://devforum.zoom.us/t/response-duplicate-meeting-id-while-using-zoom-api/116380/1 "2024-08-26T09:06:05Z")

</div>

Hi, i have a issue about meeting ids.

i sent this url `zoomurl/v2/users/#{userid}/meetings`  
then it returned same or used meeting id.

and i sent ‘zoomurl/v2/meetings+ meetingId’ using the returned meeting id but returned this message

`Response Body: {"code":3001,"message":"Meeting does not exist: meetingId."}`

I think it’s because it’s a meeting ID I’ve already used.  
Since this problem occurred today maby 12 pm , how can I solve it?

Please reply, Thank you.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [August 26, 2024, 6:10pm UTC](https://devforum.zoom.us/t/response-duplicate-meeting-id-while-using-zoom-api/116380/2 "2024-08-26T18:10:27Z")

</div>

Hi @secure  
Thanks for bringing this to our attention.  
Are you still having this issue and is this happening to all your meetings?  
could you share the meeting ID with me so I can take a closer look at this

---

<div class="post-metadata">

**Author:** ![secure](https://avatars.discourse-cdn.com/v4/letter/s/edb3f5/32.png) [@secure](https://devforum.zoom.us/u/secure)\
**Post date:** [August 27, 2024, 1:37am UTC](https://devforum.zoom.us/t/response-duplicate-meeting-id-while-using-zoom-api/116380/3 "2024-08-27T01:37:18Z")

</div>

Hello, Elisa

Thank your reply.

i still having this issue and all my meetings.

my clients didn’t use zoom meeting from yesterday.

i am trying about things but i can’t resolve:(

we use meeting IDs but i share one meeting IDs ‘86945079565’.

if you need all IDs then reply to me!

Thank you and i wait your reply.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [August 27, 2024, 5:21pm UTC](https://devforum.zoom.us/t/response-duplicate-meeting-id-while-using-zoom-api/116380/4 "2024-08-27T17:21:05Z")

</div>

@secure  
I am not able to see the meeting you shared in our backend. I will send you a DM to get more information about this

---

<div class="post-metadata">

**Author:** ![secure](https://avatars.discourse-cdn.com/v4/letter/s/edb3f5/32.png) [@secure](https://devforum.zoom.us/u/secure)\
**Post date:** [August 28, 2024, 1:00am UTC](https://devforum.zoom.us/t/response-duplicate-meeting-id-while-using-zoom-api/116380/5 "2024-08-28T01:00:44Z")

</div>

Where can I check DM?

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [August 29, 2024, 12:01pm UTC](https://devforum.zoom.us/t/response-duplicate-meeting-id-while-using-zoom-api/116380/6 "2024-08-29T12:01:54Z")

</div>

on the top right corner you should see a notification

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [September 2, 2025, 3:37am UTC](https://devforum.zoom.us/t/response-duplicate-meeting-id-while-using-zoom-api/116380/7 "2025-09-02T03:37:59Z")

</div>

Closed on September 2, 2025, 3:37am UTC

This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.
