
Rate Limiting and the Webex API
developer.ciscospark.com ciscospark.com
This is what was read here when it was published. Taylor Hanson no longer carries it in what it publishes now.
Listen to this summary
In this blog, we’ll provide a guide to implementing rate limiting with the Webex API to gracefully allocate resources across the shared Webex customer base, preventing excessive request errors in your own app, and ensure efficient API call management. We’ll examine practical solutions like using the Retry-After header to handle HTTP 429 errors and offers a Python code example for seamless integration in your own environment.
To protect the Webex environment, especially from distributed denial of service attacks, the API has rate limits in place for the different resources available for use, such as /messages and /rooms. These limits will vary depending on the calls being made, how resource intensive that call is on the servers, and how many servers are actively in routing – and is subject to change as needed to protect all use cases from failing in the event of a large batch of requests.
More ways to use this
Open on another device
Scan to open this page. Your saved notes and account access are not included.