Cisco Webex · Rate Limits
Cisco Webex Rate Limits
Webex for Developers enforces dynamic rate limits on its REST APIs. Limits are scoped per application and per organization, vary by endpoint family (Messaging, Meetings, Admin, xAPI), and return HTTP 429 with a Retry-After header when exceeded. Webex publishes guidance on backoff and on requesting a higher limit through Cisco support.
3 Limits
Throttle: 429
CollaborationVideo ConferencingMessagingRate Limiting
Limits
Default REST API limit app/organization
see Webex for Developers Basics; per-endpoint dynamic limits
Bot / integration messaging limit app/bot
see Webex for Developers Basics; messaging endpoints have stricter caps to prevent spam
Admin / Control Hub APIs organization
see Webex for Developers Basics
Policies
Backoff Strategy
On HTTP 429, honor the Retry-After response header and apply exponential backoff with jitter before retrying. Do not retry without delay.
Trackingid for support
Include the Trackingid response header value when contacting Cisco support to raise a limit or investigate throttling.
Limit increase request
Production integrations that need higher throughput can request a limit increase via Webex Developer Support.
Pagination and webhooks
Use webhooks and pagination instead of polling — large list endpoints are explicitly throttled to encourage event-driven access patterns.