Source note · Troubleshooting Webex Contact Center API errors
Passing a Base64 Webex platform organization ID where a WxCC API expects the raw org UUID (the form found at the end of the access token) is a plausible cause of 403 or 404 responses.
inferred · Checked 2026-10-02
- Vendor
- Cisco
- Product
- Webex Contact Center
- Subsystem
- identifiers
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Status
- inferred
- Checked
- 2026-10-02
Sources
- What the Base? Decoding Webex API IDs — Cisco Webex for Developers · tier 2 current vendor documentation · decoded format section, read with the orgId extraction sample 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-orgid-format-mismatch-infer. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxcc-api-errors-troubleshooting-orgid-format-mismatch-infer
BibTeX
@misc{warmtransfer-claim-wxcc-api-errors-troubleshooting-orgid-format-mismatch-infer,
title = {Troubleshooting Webex Contact Center API errors: source note wxcc-api-errors-troubleshooting-orgid-format-mismatch-infer},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxcc-api-errors-troubleshooting-orgid-format-mismatch-infer},
note = {Source note wxcc-api-errors-troubleshooting-orgid-format-mismatch-infer, checked 2026-10-02}
}