Source record · tier 2 current vendor documentation
Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center
- Publisher
- Cisco
- URL
- https://www.cisco.com/c/en/us/support/docs/contact-center/webex-contact-center/217735-configure-http-request-on-call-flows-wit.html
- Published
- 2022-03-11
- Updated
- unknown
- Accessed
- 2026-09-22
- HTTP status
- 200
- License
- Cisco website terms of use; no-redistribution; short excerpts and locators only
Source notes citing this source
- Cisco's technote places a Case node right after the HTTP Request node to branch on the HTTP status code and confirm a 200 OK response. in context
- Without an authenticated endpoint, the HTTP Request activity takes the full request URL (domain and path), and an authorization value can be supplied as a request header. in context
- Cisco advises running the API in Postman or another API tool to confirm it returns 200 OK before using it in an HTTP Request activity. in context
- Cisco guidance is to put a Case activity after the HTTP Request activity and branch on the returned HTTP status code (httpStatusCode), for example to check for 200 OK and to handle each error code the target API defines. in context
- With a connector, the connector's Resource Domain holds only the host part of the URL, and the HTTP Request activity holds the request path; putting the path in the connector domain, or the domain in the path, is a configuration mistake. in context
- To call an endpoint with Basic authentication without a connector, turn off 'Use Authenticated Endpoint', enter the full URL, and add an Authorization header whose value is 'Basic' followed by the Base64 encoding of username:password. in context
- Because Cisco tells developers to check the status code in a Case activity, a non-2xx HTTP response probably continues down the activity's normal output rather than the error path, so a flow with no status check can silently carry on with bad data. inferred in context
- Cisco TAC recommends testing the target API outside the flow first, for example in Postman, and confirming a 200 OK before configuring the HTTP Request activity. in context
Cite this source record
APA
WarmTransfer. (2022, March 11). Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-technote-217735-http-request-basic-auth
BibTeX
@misc{warmtransfer-cisco-technote-217735-http-request-basic-auth,
title = {Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center},
author = {{WarmTransfer}},
year = {2022},
url = {https://warmtransfer.net/knowledge/sources/cisco-technote-217735-http-request-basic-auth},
note = {Cisco, accessed 2026-09-22}
}