Skip to Content
avatar image
Former Member

Sender JSON Request escapes characters - REST Receiver Adapter

I have a iDoc -> JSON scenario and use the REST Adapter.

This is a 1:N scenario and I use a XSLT mapping to do the mapping.

When sending out messages, the messages fail due to 'bad request'

When looking in the monitoring I see my request has escaped characters, e.g. \n and \t and \"

See below:

"{\"accountclassificationcode\":\"10\",\"accountnumber\":\"0000000555\",\"lc_title\":\"Company\",\t\t\"lc_accounttype\":\"1\",\t\t \"fax\":\"+31 99999999\",\"emailaddress1\":\"info@website.nl\",\"lc_brandidentity\":\"\",\"lc_accountname1\":\"Accountname - tes\",\"lc_city\":\"AMSTERDAM\",\"lc_creditrating\":\"2A1\",\"lc_incoterm\":\"FH\",\"lc_lcpackstore\": false,\"lc_bigbagswarehouse\": false,\"lc_pobox\":\"137\",\"lc_popostalcode\":\"1111 AC\",\"lc_postalcode\":\"1111 LV\",\"lc_searchterms\":\"PACK\",\"lc_street\":\"Weg 150\",\"lc_taxnumber\":\"9999999\",\"lc_vatnumber\":\"NL999999B01\",\"telephone1\":\"+31 999999999\",\"lc_paymentterms\":\"D030\",\"statecode\":1,\"statuscode\":2}\n\t\t\t"

In the monitoring I also see that Content Type is set as "text/plain", however in the REST Receiver channel I have created a HTTP header of Content-Type = application/json

Does anyone know why this is? And how to solve this?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers