Source note · Troubleshooting Webex Contact Center API errors
A WxCC 403 with a fresh token most likely means the token lacks a required scope (for example cjp:config_read or cjp:config_write), the authorizing user lacks the needed admin or supervisor role, or the request targets an orgId other than the token's org.
inferred · Checked 2026-10-02
- Vendor
- Cisco
- Product
- Webex Contact Center
- Subsystem
- REST API error responses
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Status
- inferred
- Checked
- 2026-10-02
Sources
- The A-Z of Webex Contact Center APIs: Capture APIs — Cisco Systems (Webex for Developers blog) · tier 2 current vendor documentation · Subscriptions API scopes, read with the 403 description in gh-webex-openapi-specs-wxcc and the orgId extraction in webex-dev-blog-wxcc-api-authentication
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting Webex Contact Center API errors: source note wxcc-api-errors-troubleshooting-forbidden-scope-role-infer. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxcc-api-errors-troubleshooting-forbidden-scope-role-infer
BibTeX
@misc{warmtransfer-claim-wxcc-api-errors-troubleshooting-forbidden-scope-role-infer,
title = {Troubleshooting Webex Contact Center API errors: source note wxcc-api-errors-troubleshooting-forbidden-scope-role-infer},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxcc-api-errors-troubleshooting-forbidden-scope-role-infer},
note = {Source note wxcc-api-errors-troubleshooting-forbidden-scope-role-infer, checked 2026-10-02}
}