Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Fail Data Actions API message

  • 1.  Fail Data Actions API message

    Posted 06-05-2025 18:43

    kike_zelenza | 2021-05-14 09:33:24 UTC | #1

    Good morning, can you help me solve this error?

    API: /api/v2/conversations/messages

    { "message": "The request could not be understood by the server due to malformed syntax.", "code": "bad.request", "status": 400, "messageParams": {}, "contextId": "8750e87b-1027-4306-a01a-b52d1efca5f1", "details": [ { "errorCode": "ACTION.PROCESSING" } ], "errors": [ { "message": "REST call for action execute failed. Message:requestUrlTemplate could not be resolved into a fully qualified URL. [8750e87b-1027-4306-a01a-b52d1efca5f1]", "code": "BAD_REQUEST", "status": 400, "messageParams": {}, "details": [], "errors": [] } ] }

    anon11147534 | 2021-05-14 09:51:46 UTC | #2

    Hi,

    Could you post the request body here with any PII redacted please.

    kike_zelenza | 2021-05-14 10:05:43 UTC | #3

    { "requestUrlTemplate": "/api/v2/conversations/messages/${input.queueId}", "requestType": "POST", "headers": { "Content-Tyoe": "application/json" }, "requestTemplate": "${input.rawRequest}" }

    Thnx

    Jason_Mathison | 2021-05-14 11:06:02 UTC | #4

    Hi Kike,

    My guess is that you are using the "Web Service data action integration", however since you are attempting to connect to Genesys Cloud, you should be using a "Genesys Cloud data action integration".

    https://help.mypurecloud.com/articles/about-genesys-cloud-data-actions-integration/

    --Jason

    kike_zelenza | 2021-05-14 11:19:31 UTC | #5

    Hello Jason,

    I am using the genesys cloud.

    kike_zelenza | 2021-05-14 11:23:58 UTC | #6

    And if I do it with another integration of genesys cloud data actions. It indicates this to me.

    body: { "requestUrlTemplate": "/api/v2/conversations/messages/${input.queueId}", "requestType": "POST", "headers": {}, "requestTemplate": "${input.rawRequest}" }

    { "message": "Method Not Allowed", "code": "method not allowed", "status": 405, "messageParams": {}, "contextId": "76701692-d0fe-42e0-8747-14e8dc8bab73", "details": [ { "errorCode": "ACTION.REMOTEENDPOINT" } ], "errors": [ { "message": "REST call for action execute failed. Message:Request to backend service failed. Response from web service: {\"message\":\"HTTP 405 Method Not Allowed\",\"code\":\"method not allowed\",\"status\":405,\"contextId\":\"57553c76-e904-46d8-a055-82ebd49addde\",\"details\":[],\"errors\":[]} [76701692-d0fe-42e0-8747-14e8dc8bab73]", "code": "INTERNALSERVER_ERROR", "status": 405, "messageParams": {}, "details": [], "errors": [] } ] }

    Jason_Mathison | 2021-05-14 12:59:46 UTC | #7

    The first action that you posted about is definitely not part of a "Genesys Cloud data action integration", it is part of a "Web Services data action integration". Web service actions need a full URL like https://foo.com/bar while Genesys Cloud actions only expect the /url/part/of/the?path

    kike_zelenza | 2021-05-14 14:47:09 UTC | #8

    And if I do it with another integration of genesys cloud data actions. It indicates this to me.

    body: { "requestUrlTemplate": "/api/v2/conversations/messages/{input.queueId}", "requestType": "POST", "headers": {}, "requestTemplate": "{input.rawRequest}" }

    { "message": "Method Not Allowed", "code": "method not allowed", "status": 405, "messageParams": {}, "contextId": "76701692-d0fe-42e0-8747-14e8dc8bab73", "details": [ { "errorCode": "ACTION.REMOTEENDPOINT" } ], "errors": [ { "message": "REST call for action execute failed. Message:Request to backend service failed. Response from web service: {"message":"HTTP 405 Method Not Allowed","code":"method not allowed","status":405,"contextId":"57553c76-e904-46d8-a055-82ebd49addde","details":[],"errors":[]} [76701692-d0fe-42e0-8747-14e8dc8bab73]", "code": "INTERNALSERVER_ERROR", "status": 405, "messageParams": {}, "details": [], "errors": [] } ] }

    Jason_Mathison | 2021-05-15 01:58:33 UTC | #9

    What Genesys Cloud API are you attempting to use? I don't see any POST in /api/v2/conversations/messages/ that expects a queueId in the URL.

    --Jason

    system | 2021-06-15 02:12:41 UTC | #10

    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: 10918



Related Content