IBX Connect - Inbound validation failures
In the following some common scenarios are described where transactions are rejected by the IBX Connect platform due to inbound validation errors. The sender is notified about those events synchronously with an HTTP response (HTTP response code 400 or similar) including a SOAP response with a brief error description.
Errors in the HTTP request structure
The HTTP request does not contain
any message in the body or the content-type in the HTTP header is not "ifrm/xml",
"multipart/related" or "application/soap+xml":
Request : Response
The login credentials in the HTTP request are missing:
Request : Response
The login credentials in the HTTP request are not valid:
Request : Response
The content type in the HTTP body is not "multipart/related" while Message is MIME:
Request : Response
Errors in the XML message in the HTTP
request body
A mandatory element is missing in the XML document which therefore is not valid according to its XML schema:
Request : Response
The receiverID in the SOAP envelope does not match any
of the trading partner profiles registered on the IBX
Connect platform (optional):
Response
The namespace of the XML payload root element is missing, hence the document type is not recognized:
Request : Response
The size of the message exceeds 7.5 MB:
Response