Source note · Troubleshooting Webex Contact Center API errors
Registering WxCC webhooks needs an admin-type token with cjp:config or cjp:config_read, whereas the Subscribe Notification WebSocket alternative works with an agent token holding cjp:user.
Checked 2026-10-02
- Vendor
- Cisco
- Product
- Webex Contact Center
- Subsystem
- subscriptions and webhooks
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- The A-Z of Webex Contact Center APIs: Agents — Cisco Webex for Developers · tier 2 current vendor documentation · webhooks and WebSocket alternative section
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting Webex Contact Center API errors: source note wxcc-api-errors-troubleshooting-webhook-vs-websocket-scopes. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxcc-api-errors-troubleshooting-webhook-vs-websocket-scopes
BibTeX
@misc{warmtransfer-claim-wxcc-api-errors-troubleshooting-webhook-vs-websocket-scopes,
title = {Troubleshooting Webex Contact Center API errors: source note wxcc-api-errors-troubleshooting-webhook-vs-websocket-scopes},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxcc-api-errors-troubleshooting-webhook-vs-websocket-scopes},
note = {Source note wxcc-api-errors-troubleshooting-webhook-vs-websocket-scopes, checked 2026-10-02}
}