# User is not registered for all provided occurrence\_ids

**URL:** <https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566>\
**Category:** API and Webhooks\
**Created:** [January 12, 2022, 2:28pm UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566 "2022-01-12T14:28:33Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![hlib](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hlib/32/34035_2.png) [@hlib](https://devforum.zoom.us/u/hlib)\
**Post date:** [January 12, 2022, 2:28pm UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/1 "2022-01-12T14:28:33Z")

</div>

## User is not registered for all provided occurrence\_ids

**Description**  
When I send add registrant request with list of occurrences - user is registered only for one occurrence

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

**Which Endpoint/s?**  
POST /meetings/{meetingId}/registrants?occurrence\_ids=

**How To Reproduce (If applicable)**

For example when I send request POST /meetings/89133870939/registrants?occurrence\_ids=1642711140000,1642365540000,1643056740000 - I see that user was added only for occurrence 1642365540000 which is very strange.

---

<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:** [January 13, 2022, 9:22pm UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/2 "2022-01-13T21:22:49Z")

</div>

Hi @hlib

Thanks for reaching out to the Zoom Developer Support! I am happy to help here!  
Is this happening for one particular meeting or happening for all the meetings that you are trying to add registrants too.

I will debug on my side and try to reproduce this issue to come back to you  
Best,  
Elisa

---

<div class="post-metadata">

**Author:** ![hlib](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hlib/32/34035_2.png) [@hlib](https://devforum.zoom.us/u/hlib)\
**Post date:** [January 14, 2022, 11:04am UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/3 "2022-01-14T11:04:37Z")

</div>

Hi, @elisa.zoom ! Thank you for your reply. It is happening for all meetings that I am trying. So every time I send request with list of several occurrences - registrant is added only to 1 occurrence from my list.

---

<div class="post-metadata">

**Author:** ![hlib](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hlib/32/34035_2.png) [@hlib](https://devforum.zoom.us/u/hlib)\
**Post date:** [January 18, 2022, 11:40am UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/4 "2022-01-18T11:40:59Z")

</div>

Hi, @elisa.zoom ! Are there some updates about this?

---

<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:** [January 19, 2022, 12:33am UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/5 "2022-01-19T00:33:05Z")

</div>

Hi @hlib

Thanks for your patience! I was able to do some testing on my side and I noticed that when you create a recurrent meeting, you can pass certain settings on your request body

 ![Screen Shot 2022-01-18 at 6.30.54 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/4/1/4174aca932acc7fe2bc80024daf0c597eb0f222b.png)

Can you please make sure that when you are creating this recurrent meeting, you are enabling registration\_type=1 so you will only need to add the registrants once and they will be able to attend any meeting occurrence.

If this is not helpful, could you please share with me the entire request body that you are sending when creating this series of meetings?

Best,  
Elisa

---

<div class="post-metadata">

**Author:** ![hlib](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hlib/32/34035_2.png) [@hlib](https://devforum.zoom.us/u/hlib)\
**Post date:** [January 19, 2022, 9:01am UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/6 "2022-01-19T09:01:47Z")

</div>

Hi, @elisa.zoom . Sorry, but it is not our business model. Our meetings are created with registration\_type=2 as each occurrence is separate ticket. Usually users buy 1 tickets but sometimes they can buy for example ticket for 5 occurrences for meeting of 10 occurrences. All was working but then we notices that you have added limits and we can send only 3 registration requests for 1 user for 1 meeting during 1 day. So I found that if needed we can make 1 call with list of occurrences but for some reason it register user only for 1 random occurrence from the list.

---

<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:** [January 19, 2022, 7:39pm UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/7 "2022-01-19T19:39:00Z")

</div>

Hi @hlib  
Ah I see! Thank you so much for sharing this with me.  
I have done some testing on my end and I was able to reproduce this behavior.  
I have created a ticket about this and will update you as soon as I hear back from our Engineering team (ZOOM-340561 for referenct)

Thanks for your patience while I investigate this issue further  
Best,  
Elisa

---

<div class="post-metadata">

**Author:** ![hlib](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hlib/32/34035_2.png) [@hlib](https://devforum.zoom.us/u/hlib)\
**Post date:** [January 20, 2022, 4:06pm UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/8 "2022-01-20T16:06:17Z")

</div>

Thank you @elisa.zoom . Do you know some estimations when this will be fixed. And also maybe you can remove limit for 3 registration calls for 1 user for 1 meeting during 1 day until this is fixed? As this is the only feature that allows to register user for several occurrences of the meeting without rate limit but it doesn’t work.

---

<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:** [January 21, 2022, 2:47pm UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/9 "2022-01-21T14:47:19Z")

</div>

Hi @hlib  
Thanks for your patience while I investigate this issue further  
I heard back from our Engineering team about this issue and they have confirmed that the behavior you are seeings is actually our design.

If a recurring meeting is configured with “Attendees need to register for each occurrence to attend” registration mode, it needs the user to register to each occurrence, also you can see the registration page in the web, you only can choose one occurrence, please see the below screenshot,

 ![Screen Shot 2022-01-21 at 8.35.32 AM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/4/5/4558d1f043bf326fd239cf5ab17e7a83adbeede1.png)

The query parameter

 ![Screen Shot 2022-01-21 at 8.44.08 AM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/4/1/41be815b723a23531eaf28cfac484b60720ca8f7.png)  
will only work for meetings with “Allow Attendees register once and can attend any of the occurrences”

Unfortunately I can not remove the limit of 3 registration calls for 1 user for 1 meeting during 1 day.

Cheers,  
Elisa

---

<div class="post-metadata">

**Author:** ![hlib](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hlib/32/34035_2.png) [@hlib](https://devforum.zoom.us/u/hlib)\
**Post date:** [January 21, 2022, 5:04pm UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/10 "2022-01-21T17:04:23Z")

</div>

Hi @elisa.zoom . This is awful behaviour. It has no sense to work only for “Attendees register once and can attend any meeting occurrences”. What is the sense to pass list of occurrences here if user register only once and then can enter every occurrence anyway? And opposite - In “Attendees must register foreach meeting occurrence” it has sense as we need somehow specify which occurrences we allow user to attend. So you added limit for 1 day for 1 user for 1 meeting and on your forums you are telling to user occurrence\_ids parameter in one call to avoid rate limit but finally occurrence\_ids parameter also doesn’t work. So there is no solution at all, isn’t it? You definitely should at least remove limit for meetings with type 2 if solution you made to avoid rate limit doesn’t work for meeting with type=2

---

<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:** [January 26, 2022, 2:21am UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/11 "2022-01-26T02:21:19Z")

</div>

Hi @hlib  
I understand how this can be inconvenient for you  
The limit for this endpoint is actually 3 requests for the same user to the same meeting ID.

---

<div class="post-metadata">

**Author:** ![hlib](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hlib/32/34035_2.png) [@hlib](https://devforum.zoom.us/u/hlib)\
**Post date:** [February 2, 2022, 11:31am UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/12 "2022-02-02T11:31:16Z")

</div>

Hi @elisa.zoom . It doesn’t look like you understand ☹ As you are putting limits and restrictions which can’t be solved. It is bug, not feature.

---

<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:** [February 3, 2022, 11:41pm UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/13 "2022-02-03T23:41:54Z")

</div>

Hi @hlib  
This change on our API was intended and I am sorry for any inconvenience that this might have cause you

---

<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:** [March 6, 2022, 9:41am UTC](https://devforum.zoom.us/t/user-is-not-registered-for-all-provided-occurrence-ids/62566/14 "2022-03-06T09:41:55Z")

</div>

Closed on March 6, 2022, 9:41am UTC

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