# Webex Contact Center APIs and webhooks Canonical: https://warmtransfer.net/knowledge/webex-cc-apis Last verified: 2026-09-16 Cisco presents the Webex Customer Experience developer surface across 3 interface styles: RESTful resources, GraphQL, and webhooks[^7]. The interfaces support return data in the application/json format only, and each endpoint page includes a Try Out control that takes an access token and parameters to produce a copyable cURL statement[^6]. ## Interface styles The RESTful interface exposes resources such as `/agents`, with methods cataloged under the API Reference[^7]. Webhooks are offered by Cisco as an alternative to slow batch reporting or expensive API polling and diffing[^7]. The GraphQL interface functions as the Search API, located under Search and then Search Tasks[^3]. Cisco describes a task as representing an incoming request or demand for work directed to agents, which can be generated for any media type, including telephony, chat, and email[^3]. Cisco positions GraphQL within this surface for extracting only relevant fields[^7]. ## Rate limits and throttling Webex Contact Center organizes API rate limits into 4 tiers based on an organization's user count[^2]: | Tier | Organization users | Rate limit | | --- | --- | --- | | Default Tier | 0 to 300 | 300 per minute, 30 per second |[^2] | Partner Tier 1 | 301 to 4000 | 1000 per minute, 100 per second |[^2] | Partner Tier 2 | 4001 to 10000 | 2000 per minute, 175 per second |[^2] | Partner Tier 3 | More than 10000 | 6000 per minute, 300 per second |[^2] In the field, documentation shows a discrepancy: the prose states that default rate limits support organizations with up to 250 users and directs organizations with more than 250 users needing higher limits to Developer Support, whereas the accompanying table defines the Default Tier as covering 0 to 300 users[^5]. When an API request is rate-limited, it returns an HTTP 429 response accompanied by a `Retry-After` header specifying a duration in seconds[^1]. The rate-limited request is not processed, and Cisco states that retrying prior to the expiration of the `Retry-After` duration results in an additional HTTP 429 response[^1]. Before reaching out to Cisco regarding rate limits, Cisco asks developers to adopt several architectural practices: - Subscribe to webhooks instead of polling[^4]. - Stagger polling across different organizations or jobs throughout the interval[^4]. - Apply internal per-customer limits[^4]. - Aggregate individual requests into batch or bulk calls[^4]. - Avoid requesting unneeded pages[^4]. - Honor the `Retry-After` duration within background tasks and enforce a maximum retry count[^4]. ## See also - See also [Webex Calling administration APIs and scopes](https://warmtransfer.net/knowledge/webex-calling-apis). - See also [What a Webex webhook guarantees](https://warmtransfer.net/knowledge/webex-calling-webhook-delivery). - See also [Webex Contact Center system limits reference](https://warmtransfer.net/knowledge/webex-cc-system-limits). ## Applicability Applies to: Cisco Webex Contact Center. Sources checked 2026-09-16. ## What remains uncertain - The GraphQL schema of the Search API and the specific fields a task exposes are not covered by the sources below. - The content of the Using Webhooks guide referenced in the overview is not covered by the sources below. - The specific OAuth scopes required by each Webex Contact Center API are not covered by the sources below. - Whether the rate limit tiers apply per token, per organization, or per endpoint is not covered by the sources below. - Whether the default rate limit tier ends at 250 users or 300 users is not covered by the sources below. - The details of any gRPC interface on this platform are not covered by the sources below. ## Sources [^1]: A rate limited Webex Contact Center request returns HTTP 429 with a Retry-After header giving a duration in seconds, the request is not processed, and Cisco states that retrying before that duration has passed yields another 429. Source: [Webex for Developers — Rate Limiting](https://developer.webex.com/webex-contact-center/docs/rate-limiting), Response Format. Checked 2026-09-16. [^2]: Webex Contact Center publishes 4 API rate limit tiers by organisation user count: a Default Tier for 0 to 300 users at 300 requests per minute and 30 per second, Partner Tier 1 for 301 to 4000 users at 1000 per minute and 100 per second, Partner Tier 2 for 4001 to 10000 users at 2000 per minute and 175 per second, and Partner Tier 3 for more than 10000 users at 6000 per minute and 300 per second. Source: [Webex for Developers — Rate Limiting](https://developer.webex.com/webex-contact-center/docs/rate-limiting), Increasing Rate Limits, Rate Limit Tiers table, read as cells. Checked 2026-09-16. [^3]: The Webex Customer Experience GraphQL interface is the Search API, found under Search then Search Tasks, and Cisco describes a task as representing the request or demand for work from the agents which can be created for any media type including telephony chat and email. Source: [Webex for Developers — Introduction to APIs](https://developer.webex.com/docs/contact-center), Introduction to APIs, GraphQL section. Checked 2026-09-16. [^4]: Before contacting Cisco about a Webex Contact Center rate limit, Cisco asks a developer to subscribe to webhooks rather than poll, to stagger polling for different organisations or jobs within the interval, to impose its own per-customer limits, to aggregate requests into batch or bulk calls, to avoid requesting unnecessary pages, to respect the Retry-After header in background tasks and to implement a maximum retry count. Source: [Webex for Developers — Rate Limiting](https://developer.webex.com/webex-contact-center/docs/rate-limiting), Best Practices, Architectural and Coding. Checked 2026-09-16. [^5]: The Webex Contact Center rate limiting page states in prose that default rate limits support organisations with up to 250 users and that an organisation with more than 250 users needing higher limits should contact Developer Support, while the table immediately below gives the Default Tier a range of 0 to 300 users (field report). Source: [Webex for Developers — Rate Limiting](https://developer.webex.com/webex-contact-center/docs/rate-limiting), Increasing Rate Limits, paragraph against the table's Default Tier row. Checked 2026-09-16. [^6]: Cisco states that the Webex Customer Experience APIs currently support return data in the application slash JSON format only, and that a Try Out control on each endpoint page accepts an access token and parameters and yields a copyable cURL statement. Source: [Webex for Developers — Introduction to APIs](https://developer.webex.com/docs/contact-center), Introduction to APIs, REST section. Checked 2026-09-16. [^7]: Cisco presents the Webex Customer Experience developer surface in 3 interface styles: RESTful resources such as slash agents whose methods are listed under API Reference, GraphQL for extracting only the relevant fields, and webhooks which it offers as the alternative to slow batch reports or expensive API polling and diffing. Source: [Webex for Developers — Introduction to APIs](https://developer.webex.com/docs/contact-center), Introduction to APIs, REST GraphQL and Webhooks sections. Checked 2026-09-16. [^8]: The government edition exposes 6 named component interfaces: the Finesse interface, an outbound campaign management interface, a precision routing interface, Customer Voice Portal Call Studio integrations, a database lookup and application gateway, and a Unified Intelligence Center reporting interface. Source: [Webex Contact Center Enterprise for Government Data Sheet](https://www.cisco.com/c/en/us/products/collateral/contact-center/webex-contact-center-enterprise/webex-cc-enterprise-govt-ds.html), Table 1, interfaces row. Checked 2026-09-05.