Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Problem with Web Services Data Actions

  • 1.  Problem with Web Services Data Actions

    Posted 06-05-2025 18:40

    DaviniaGarridoLope | 2018-01-03 15:37:35 UTC | #1

    I have created a web service data action integration. I need to send some parameters to an external Web Service.

    Input Contracts

    { "$schema": "http://json-schema.org/draft-04/schema#", "type": "object", "required": [ "ANI" ], "properties": { "ANI": { "type": "string", "description": "ANI" } } }

    Output contracts

    { "properties": {} }

    Request Configuration

    { "requestUrlTemplate": "https://servicios.XXXXXXXXXX.com/survey/XXXXXXXXXXXX/v1/load", "requestType": "POST", "headers": { "Content-Type": "application/json" }, "requestTemplate": "${input.rawRequest}" }

    Response Configuration

    { "translationMap": {}, "successTemplate": "${rawResult}" }

    But I get the following error:

    { "status": 500, "code": "internal.server.error", "message": "The server encountered an unexpected condition which prevented it from fulfilling the request.", "messageParams": {}, "contextId": "64200d50-c655-4942-9b8f-7270b40a26c1", "details": [], "errors": [ { "status": 200, "code": "INTERNALSERVERERROR", "message": "REST call for action execute failed. Message:We were unable to process the response from the remote endpoint (servicios.XXXXXXXXX.com) because it had a 'content-type' header of 'text/plain; charset=UTF-8' instead of the required value of 'application/json'. [64200d50-c655-4942-9b8f-7270b40a26c1] [64200d50-c655-4942-9b8f-7270b40a26c1]", "messageParams": {}, "details": [], "errors": [] } ] }

    Is this a data action configuration problem or is a web service problem? I have tried it in Postman and I don't get any errors.

    Thanks in advance!

    Jason_Mathison | 2018-01-03 13:22:52 UTC | #2

    This is a problem with the servicios.ydilo.com web service. It is responding back with the wrong content type.

    I tried to reproduce this issue in postman, however I was getting the correct content type of application/json back. Are you still having this issue?

    The only change I had to make to get your action to work was to change the success Template to "successTemplate": "{}"

    DaviniaGarridoLope | 2018-01-03 14:00:25 UTC | #3

    No, the problem is solved. I spoke to them this morning to see if they could change their header and now it works. Thank you!

    system | 2018-02-03 14:10:58 UTC | #4

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



Related Content