CreateBlogSupport
Log inSign up
Home
Webex Contact Center
  • Overview
  • Guides
  • API REFERENCE
  • AI
  • Configuration
  • Data
  • Desktop
  • Journey
  • Media And Routing
  • Customer Journey Data Service
  • Webhooks
  • Changelog
  • Contact Center Sandbox
  • Using Webhooks
  • Beta Program
  • Webex Status API
  • XML API Deprecation

Webex Contact Center

Rate Limiting

Navigating Rate Limits for Webex Contact Center APIs

Webex Contact Center APIs are also protected with rate limiting. You are responsible for architecting and coding your application responsibly so as to not create too much traffic. The token generated by this Portal has special rate limit restrictions and is not suitable for production use. Follow the Authentication guide to experience realistic rate limit restrictions.

Note: The current default rate limit for a given client ID is 300 requests per minute.

anchorResponse Format

anchor

Every rate limited request will have a 429 response with a retry-after header included. This means your request has not been processed. Do not try again until after the retry-after duration (in seconds) has passed, else you will receive another 429 response. For example, a 4 second wait time will look like so:

Retry-After: 4

anchorBest Practices

anchor

Before contacting Cisco for any rate limit issues, make sure you are following API best practices:

Architectural
  • If you are polling an API to find changes, consider subscribing to webhooks instead.
  • If you are polling on a regular interval (hourly, every 15 minutes, etc.), consider scheduling different organizations or jobs at different times within the interval, perhaps using a hash.
  • Consider implementing your own limits to prevent a single customer from causing your app to exceed rate limits.
  • Consider aggregating requests and using batch or bulk APIs.
  • For paginated APIs, avoid requesting unnecessary pages.
Coding
  • User requests: Provide immediate feedback to users, suggesting a retry and displaying the retry-after value.
  • Background tasks: Respect the retry-after header by waiting the specified duration before retrying.
  • Prevent infinite retries: Implement a maximum retry count.
Increasing Rate Limits

Webex Contact Center prioritizes the security of our systems and customer data by continuously monitoring network traffic. To help developers get started and support organizations with up to 250 users, we offer default rate limits. If your organization has more than 250 users and requires higher rate limits, please contact Developer Support to discuss your specific needs.

Rate Limit Tiers

Rate Limit TierNo. of UsersRequests per minuteRequests per second
Default Tier0 - 300300 rpm30 rps
Partner Tier 1301 - 40001000 rpm100 rps
Partner Tier 24001 - 100002000 rpm175 rps
Partner Tier 310000+5000 rpm250 rps
In This Article
  • Response Format
  • Best Practices

Connect

Support

Developer Community

Developer Events

Contact Sales

Handy Links

Webex Ambassadors

Webex App Hub

Resources

Open Source Bot Starter Kits

Download Webex

DevNet Learning Labs

Terms of Service

Privacy Policy

Cookie Policy

Trademarks

© 2025 Cisco and/or its affiliates. All rights reserved.