Webex Connect HTTP request (Captures API) problem

[maria-crowley]

I am building a live chat flow in Webex Connect, and I am using an AI agent before the chat is queued to a human agent. 

I want to use the http request node after the AI agent interaction is finished so that I can retrieve the transcript of the chat between the customer and the AI agent.

I am following the docs from this link. https://developer.webex-cx.com/documentation/captures/v1/list-captures

When I try to make an API request to this endpoint I am getting a 403 error with Authorization failed. However I am able to use other webex API's without getting this 403 error, so I don't know what the problem is.

I have inserted a picture of the http request node. 

[bill.king1]

Have you tried it as a test on the developer portal (Try Out) for your org?

[maria-crowley]

I tried that, and it is giving me the same 403 error. I have attached a screenshot below. 

[maria-crowley]

The API works when I use the Webex HTTP connector in flow designer, however I want to use this API in Webex connect and but the personal access token is not working.

[bill.king1]

Hi, and you say other APIs work in the same manner, but when you try this one, the token portion doesn't work? Like if you try other APIs in the sandbox, they all work, but when you try it for this one it doesn't?

[maria-crowley]

Yes, exactly. For example I used the try it out option for the 'Get tasks' API.  https://developer.webex-cx.com/documentation/tasks/v1/get-tasks  and that worked using the personal access token. I have included a screenshot of this with a 200 response. 

I also created an integration on the webex developers portal with the following scopes cjp:config, cjp:config_read and cjp:config:write  but when I used this token I'm still getting 403 response.

[Ove-Tolk]

Hi there,

we are currently using this endpoint as well. I'm able to run it with the access token from my integration. 

It could be a false documentation.

Add cjp:user to your configuration (I know it isn't required, but my integration got it).
Make sure to retrieve a new access token from your OAuth Authorization URL because the URL has changed.

Best regards

Ove

[maria-crowley · Accepted solution]

I have since solved the issue. I was using a premium agent user profile instead of administrator profile. Worked with the administrator profile.