Error on Body XML when posting to IPS API from Mongoose

I don't seem to be getting past error when trying to call IPS API from Mongoose.

Returns as per below:

p1: 1
p2: M3
p3: POST
p4: /ips/service/PCS260_Cost
p5: <?xml version="1.0" encoding="UTF-8" standalone="no"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="">schemas.xmlsoap.org/.../" xmlns:add="">schemas.infor.com/.../AddCost" xmlns:cred="">lawson.com/.../credentials"> <SOAP-ENV:Body><add:AddCost><add:PCS260><add:Facility>XXX</add:Facility><add:ItemNumber>ITEM123</add:ItemNumber><add:CostingDate>230316</add:CostingDate><add:CostingType>3</add:CostingType><add:CostingSum1>1234</add:CostingSum1><add:ManuallyUpdatedMark>0</add:ManuallyUpdatedMark></add:PCS260></add:AddCost></SOAP-ENV:Body></SOAP-ENV:Envelope>
p6: application/xml
timeout: 10000
binaryResponse: 0
HttpResponseCode: -1
Response:
ResponseHeaders:
InfoBar: Error parsing ION API method parameters: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.

Works great with the above XML String when calling API Manually in IONAPI Section.

Also, calling from 'Test ION API Invoke' program in Mongoose gives same error.

Anyone been able to call having an XML in the 'Body' for a POST API?

Find more posts tagged with

Accepted answers

All comments

Rene Bottern

Since I could not find a way to get through this in Mongoose, I created a .Net REST GET API instead which in turn call the M3 ips API.
This works great, since this can be called from Mongoose without any problem.

API parameters as per below.

Yao Jiang

The parameters field (p5) is expected to be in this format.

[

{

      "Name":"",

      "Type":"",

      "Value":""

]

Here is an example with xml in the parameter.

[
{
"Name": "accept",
"Type": "header",
"Value": "text/xml"
},
{
"Name": "data",
"Type": "body",
"Value": "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:prod="http://www.infor.com/businessinterface/ProductionOrder_v2">
<soapenv:Header>
<prod:Activation>
<company>1000</company>
</prod:Activation>
</soapenv:Header>
<soapenv:Body>
<prod:List>
<ListRequest>
<ControlArea>
<Filter>
<LogicalExpression>
<logicalOperator>and</logicalOperator>
<ComparisonExpression>
<comparisonOperator>like</comparisonOperator>
<attributeName>ProductionOrder_v2.orderCode</attributeName>
<instanceValue>01</instanceValue>
</ComparisonExpression>
</LogicalExpression>
</Filter>
<maxNumberOfObjects>200</maxNumberOfObjects>
</ControlArea>
</ListRequest>
</prod:List>
</soapenv:Body>
</soapenv:Envelope>"
}
]

dEPM-655.mp4

Rene Bottern

I see, that actually makes sense, thanks Yao!

Copyright © 2025 Infor. All rights reserved.