Some small issue about the api [POST /webinars/{webinarId}/registrants]

API and Webhooks Webinars
1

I would like to confirm a few details about the api

https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/webinarRegistrantCreate


Error Code: 3000

This webinar does not have registration as required: {webinarId}.

Error Code: 3000

You have reached the limit for the number of attendees you can add. Contact Zoom Support for more information.

Error Code: 3000

The Zoom REST API does not support paid registration.

The above three errors appear to have different messages, why is the code set to the same one?

Can we only judge errors based on the content of the message?


HTTP Status Code: 429

You have exceeded the daily rate limit of "{0}" for Add a webinar registrant API requests for the registrant "{1}". You can resume these API requests at GMT 00:00:00.

According to the instructions of this API, the limit should be calculated in seconds.
https://developers.zoom.us/docs/api/rest/rate-limits/
30 requests/secondļ¼Ÿ

Why it looks like we need to wait until the next day to continue using it?

2

Hi @jiangqimin
Thanks for reaching out to us!
The limit for adding registrants to a webinar/meeting was introduced last year and it limits you to only be able to add a registrant to the same webinar up to 3 times.
So what you are seeing is expected

3

@elisa.zoom

I try it ,and it looks like the limit is 3 when i want registrant with same email. thanks.

so.if I make the request over 30 requests/second, what code&message I will get ?
I want to be able to distinguish between these two situations怂

On the other side, if I send a wrong email, I get this

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<result>
    <code>300</code>
    <message>Validation Failed.</message>
    <errors>
        <field>email</field>
        <message>Invalid field.</message>
    </errors>
</result>

is there any way to make it return as json?(as the other error like)

4

I get json by set accept to ā€˜application/jsonā€™ in header. thanks.

1 Like
5

Thanks for sharing more details with me @jiangqimin
I will share your feedback to our Documentation team so they can make adjustments to it