03-28-2022 02:57 AM
Hello Webex team,
I am working with Webex REST API, especially with meetings. Even if I use an admin account, I understand that there is a rate limit that can trigger a 429 error, with a retry-after indicating when I can send a new request:
https://developer.webex.com/docs/basics#rate-limiting : some arbitrary rate limit on the whole API + 2.4k requests per minute, per account limit
https://developer.webex.com/docs/api/v1/meetings/create-a-meeting : 3k calls / 24h limit on this peculiar call
My question is: what is the "counter" strategy behind this ?
Is there a counter reset after the indicating time (e.g. 24h), or is it some rolling count strategy, every request being decremented from it after said time ?
I understand that I have to comply with the rate limit, and I already implemented the advised strategy in my application.
I ask this question for having more insight about this, and plan usage limits for my application.
Solved! Go to Solution.
03-28-2022 03:02 AM - edited 03-28-2022 03:56 AM
Hi, yes it is true that admin users can create up to 3000 meetings per day or to be exact, during a 24 hour period. For the same time period, normal hosts can only create up to 100 meetings.
The way this is enforced is that once the admin starts creating meetings, the 24hr timer will start and count the meetings created. If 3000 meetings are created before the timer ends, the user will be rate limited. If the 24hr timer ends before the user creates 3000 meetings, it will reset the timer back to full 24hrs and a new batch of 3000 meetings can be created.
One other thing to add is that there may be cases where you might get limited before reaching the 3000 meetings mark, this may happen due to server loads at that specific time. That's why it's important to adhere to the retry-after header value.
Let us know in case of any queries.
03-28-2022 03:02 AM - edited 03-28-2022 03:56 AM
Hi, yes it is true that admin users can create up to 3000 meetings per day or to be exact, during a 24 hour period. For the same time period, normal hosts can only create up to 100 meetings.
The way this is enforced is that once the admin starts creating meetings, the 24hr timer will start and count the meetings created. If 3000 meetings are created before the timer ends, the user will be rate limited. If the 24hr timer ends before the user creates 3000 meetings, it will reset the timer back to full 24hrs and a new batch of 3000 meetings can be created.
One other thing to add is that there may be cases where you might get limited before reaching the 3000 meetings mark, this may happen due to server loads at that specific time. That's why it's important to adhere to the retry-after header value.
Let us know in case of any queries.
05-16-2022 08:15 AM
Hi Raffaele, does your above statement "admin users can create up to 3000 meetings per day" mean that
Is it possible to ask for an exception, with regard to the mandatory transition from XML API to REST API?
05-16-2022 08:21 AM
I believe that it's a limit on a per admin user basis, so yes in theory it should be possible for each admin (full admin that is) to create 3k meetings each per 24 hr range.
As for asking for an exception, I am not sure why exactly that is needed but it would be best to reach out to us through a support ticket by emailing us on devsupport@webex.com. Please describe the full use case for needing this and how you are currently restricted if it isn't granted. This way we can then check with engineering through official internal channels if needed. Thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide