Source note · Calling an external API from a Webex Contact Center flow
Cisco recommends that flows calling Contact Center APIs allow for rate limiting, handle HTTP 429 responses gracefully, and handle documented API error codes with Case activities.
Checked 2026-09-30
- Vendor
- Cisco
- Product
- Webex Contact Center
- Subsystem
- Flow Designer HTTP Request activity
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Using the New HTTP Connector for Webex Contact Center APIs — Cisco Webex Developer Relations · tier 2 current vendor documentation · best practices section
Cite this note
APA
WarmTransfer. (2026, September 30). Calling an external API from a Webex Contact Center flow: source note wxcc-http-request-setup-handle-429-and-errors. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxcc-http-request-setup-handle-429-and-errors
BibTeX
@misc{warmtransfer-claim-wxcc-http-request-setup-handle-429-and-errors,
title = {Calling an external API from a Webex Contact Center flow: source note wxcc-http-request-setup-handle-429-and-errors},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxcc-http-request-setup-handle-429-and-errors},
note = {Source note wxcc-http-request-setup-handle-429-and-errors, checked 2026-09-30}
}