Issue with client token

[Ravi]

Case #0003358529
I was able to get the token using postman, but it is not working with the action..

========================================================================
When I ran the action in [ Execute] tab is showing this error in step 8.
{
"message": "The request could not be understood by the server due to malformed syntax.",
"code": "bad.request",
"status": 400,
"messageParams": {},
"contextId": "bef6e417-babd-46ec-91e0-cefb1c4ae005",
"details": [
{
"errorCode": "ACTION.REMOTE_ENDPOINT"
}
],
"errors": [
{
"message": "REST call for action execute failed. Message: Request to backend service failed. Response from web service: {\r\n "error":"invalid_request",\r\n "error_description":"Missing or duplicate parameters"\r\n} [bef6e417-babd-46ec-91e0-cefb1c4ae005]",
"code": "BAD_REQUEST",
"status": 400,
"messageParams": {},
"details": [],
"errors": []
}
]
}

In my Chrome more tool is showing the following error:{
"message": "Action with id custom_-_fd94b7c7-30ac-4ee1-bbfa-8df8fd7e81dc was not found",
"code": "not.found",
"status": 404,
"messageParams": {},
"contextId": "5b524500-bee2-427c-800c-63853ae52f7d",
"details": [
{
"errorCode": "ACTION.PROCESSING"
}
],
"errors": []
}

[Jason_Mathison]

Take a look at the way the body template is resolved. That is where you are likely to see a difference from what postman sent as its body. You will want to have the postman console open so you can see what it actually sent, not what it shows in the normal UI.

[tim.smith]

@Ravi please contact your security teams to have your OAuth credentials regenerated since your message (that I deleted) posted the client id and secret in clear text on the public internet. Please remember to always handle OAuth client secrets the same way you handle passwords.

[Ravi]

Sorry about this. Do you have an answer to my question? Where am I making the mistake?

[tim.smith]

@Ravi

"message": "REST call for action execute failed. Message: Request to backend service failed. Response from web service: {\r\n "error":"invalid_request",\r\n "error_description":"Missing or duplicate parameters"\r\n}

I'd recommend working with the team that owns the service you're calling to debug from that side. It's sending an error message back that isn't super helpful; it isn't telling you which parameter is duplicated or missing. Hopefully some server-side logging on its side can tell you exactly why it's rejecting your request. This isn't something we (Genesys) are going to be able to tell you because the error isn't originating from our side.