Got past the "Bearer Token Error" however I am getting this error below:
The below is the RAW request
{
"integrationId": "1a67a946-7afc-4a15-9601-7eab0f5bbd42",
"rawRequest": "{\"input_WantsText\":true,\"input_ANI\":\"9155259796\"}",
"input_WantsText": "true",
"input_ANI": "9155259796",
"orgId": "2381300d-0444-49d8-9c19-f4ba5407138d"
}
It is in this execute last step that it is erroring out now which it is complaining about the "input_WantsText field. Is it expecting other than a "boolean" type?
{
"message": "The request could not be understood by the server due to malformed syntax.",
"code": "bad.request",
"status": 400,
"messageParams": {},
"contextId": "58776f75-940e-4f14-a3ba-55224cb9ed34",
"details": [
{
"errorCode": "ACTION.REMOTE_ENDPOINT"
}
],
"errors": [
{
"message": "REST call for action execute failed. Message: Request to backend service failed. Response from web service: [{\"message\":\"Unrecognized field \\\"input_WantsText\\\" at [line:1, column:24]\",\"errorCode\":\"JSON_PARSER_ERROR\"}] [58776f75-940e-4f14-a3ba-55224cb9ed34]",
"code": "BAD_REQUEST",
"status": 400,
"messageParams": {},
"details": [],
"errors": []
}
]
}
When we test with postman it responds fine using this JSON which places the variables in an ARRAY and Genesys does not allow that or is there something else going on?
{
"inputs": [
{
"input_ANI": "1112223333",
"input_WantsText": true
}
]
}
Best Regards,
Francisco Amaya
BTIS - GIT ENGG SOLUTIONS
| HCLTech |
| Supercharging Progress™ |
| http://www.hcltech.com/. Click or tap if you trust this link." rel="noopener noreferrer" data-linkindex="0" data-auth="Verified" style="color: #3C91FF; margin: 0">hcltech.com |
Tel: 2679423643
::DISCLAIMER::
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
Original Message:
Sent: 5/22/2025 8:44:00 AM
From: Jason Mathison
Subject: RE: No authentication bearer token
I apologize, I forgot that test mode redacts the response. I would suggest testing both authentication and the "real" action in postman. One issue that a customer ran into before was the authentication endpoint returned something like "bearer" for the token_type, but then failed authentication if the didn't use "Bearer" (capital B). Once you know exactly how to make this work, you can verify in test mode that your headers and body are exactly the same as what is working in postman. If authentication continues to fail then probably best off opening a support ticket.
------------------------------
--Jason
------------------------------
Original Message:
Sent: 05-21-2025 13:14
From: Cisco Amaya
Subject: No authentication bearer token
How am I able to see the redacted information when running the Auth Action? I have not been able to find any information on it.
Best Regards,
Francisco Amaya
BTIS - GIT ENGG SOLUTIONS
| HCLTech |
| Supercharging Progress™ |
| http://www.hcltech.com/. Click or tap if you trust this link." rel="noopener noreferrer" data-auth="Verified" data-linkindex="0" style="color: #3C91FF; margin: 0">hcltech.com |
Tel: 2679423643
::DISCLAIMER::
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
Original Message:
Sent: 5/21/2025 9:54:00 AM
From: Jason Mathison
Subject: RE: No authentication bearer token
You can ignore this message:
Execute: No authentication bearer token specified in authorization header.
It is a hard coded error message based on the remote endpoint returning a 401 response code. We have a ticket in to get rid of this inaccurate message.
I would suggest running the auth action in test mode to see what the endpoint responds with, then try to use the token_type and access_token it returns in postman with the same configuration to see if that work.
------------------------------
--Jason
Original Message:
Sent: 05-20-2025 17:21
From: Cisco Amaya
Subject: No authentication bearer token
I created the Integration with user defined OAuth. It created the Custom Web Service authentication Action. I configured the custom Auth action and it runs with no errors. Then I created a new Data Action and configured it with below
{
"requestType": "POST",
"requestTemplate": "${input.rawRequest}",
"requestUrlTemplate": "https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"headers": {
"Authorization": "${authResponse.token_type} ${authResponse.access_token}"
}
}
When I run it it provides the error below:
Execute: No authentication bearer token specified in authorization header.
- REST call for action execute failed. Message: Request to backend service failed. Response from web service: [{"message":"Session expired or invalid","errorCode":"INVALID_SESSION_ID"}] []
so somehow the data action is unable to receive the auth response from the custom Auth action.
#DataActions
------------------------------
Cisco Amaya
------------------------------