Dodsoftware | 2019-07-27 12:37:24 UTC | #1
We're migrating from Bridge actions to Data Actions.
We set up our first Data Action. We set "configuration->Request URL Template" to something like: https://5af401XXX.ngrok.io/ivr/blacklist/check (note that the actual url is a working one)
We set "configuration->Headers" to: Transfer-Encoding - buffered
when testing it the "Perform authentication" step fails with the error below.
{ "status": 400, "code": "bad.request", "message": "The request could not be understood by the server due to malformed syntax.", "messageParams": {}, "contextId": "389d715f-2d87-40c5-be69-69d46016b250", "details": [ { "errorCode": "ACTION.PROCESSING" } ], "errors": [] }
Our api endpoint doesnt currently have any authentication requirements and we can see that no requests are making it to our server so I expect this to function like a webhook might and just hit our endpoint with the input.
I dont understand why this authentication step is taking place. Any idea why we are getting this error?
Input contract:
{ "$schema": "http://json-schema.org/draft-04/schema#", "title": "Blacklist request schema", "description": "Blacklist request schema", "type": "object", "properties": { "phonenumber": { "type": "string", "description": "The incoming number" }, "conversationid": { "type": "string", "description": "The conversation id" }, "interaction_id": { "type": "string", "description": "The interaction id" } }, "additionalProperties": true }
Output contract:
{ "$schema": "http://json-schema.org/draft-04/schema#", "title": "Blacklist response schema", "description": "Blacklist response schema", "type": "object", "properties": { "blacklisted": { "type": "boolean", "description": "True if the provided number is on our blacklist." }, "reason": { "type": "string", "description": "If blacklisted is true, the reason the number was blacklisted." } }, "additionalProperties": true }
Jason_Mathison | 2019-07-29 13:27:24 UTC | #2
Hi Wesley,
The issue is that this action is part of a "PureCloud Data Action" integration (as in, these actions are trying to execute against PureCloud in your region). By the sounds of it you want a "Web Services Data Action" integration configured with no-auth credentials.
Internally we have great logging for what is going wrong, but due to a bug on our part it is currently not making it out as a useful error message. We actually ran into exactly this issue internally last week and have a story in our backlog to return a useful error message. --Jason
system | 2019-08-29 13:27:27 UTC | #3
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 5649