Error 403: When Running Token API

I need help from the Dev Team. I'm getting a "NOT_AUTHORIZED" “403” error when running a POST Token request. I test via postman and the result is 200 OK. Not sure why Genesys is blocking the request saying it's not authorized.

Genesys API Response:
{
"message": "You are not authorized to perform the requested action.",
"code": "not.authorized",
"status": 403,
"messageParams": {},
"contextId": "88ad2722-c551-4efa-b274-77c3392c9565",
"details": [
{
"errorCode": "ACTION.REMOTE_ENDPOINT"
}
],
"errors": [
{
"message": "REST call for action execute failed. Message:Request to backend service failed. Response from web service: \r\n403 Forbidden\r\n\r\n

403 Forbidden

\r\n\r\n\r\n [88ad2722-c551-4efa-b274-77c3392c9565]",
"code": "NOT_AUTHORIZED",
"status": 403,
"messageParams": {},
"details": [],
"errors": []
}
]
}

1 Like

The request to the target service is returning the 403. You'll need to contact the owner of that service to investigate why it's failing. A 403 response generally means that you don't have the required permissions to access the resource, so it may be a configuration issue in that external service.

Hi @Tim, I thought that was the case but why would postman run the request without any restrictions?

Unfortunately, I don't have any insight into the operation of the external service to be able to tell why it's allowing one request and not the other. Investigation into that 3rd party service should yield some information about why it's allowing one request and not the other.

Okay. Thanks. I did reach out to the API owner so they can review if anything changed with the API. Thanks for your help!

If this is working in postman but not in test mode I recommend running through the steps on the Web Services tab of this page:

The first item often fixes odd issues.

--Jason

I'll review the link. Thanks, @Jason_Mathison.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.