To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /xml/reply/LaneStatusRequest HTTP/1.1
Host: booking.pufferdayspa.com
Content-Type: application/xml
Content-Length: length
<laneStatusRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://tripos.vantiv.com/2014/09/TriPos.Api">
<laneId>0</laneId>
</laneStatusRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<laneStatusResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://tripos.vantiv.com/2014/09/TriPos.Api">
<_errors>
<error>
<developerMessage>String</developerMessage>
<errorType>String</errorType>
<exceptionMessage>String</exceptionMessage>
<exceptionTypeFullName>String</exceptionTypeFullName>
<exceptionTypeShortName>String</exceptionTypeShortName>
<userMessage>String</userMessage>
</error>
</_errors>
<_hasErrors>true</_hasErrors>
<_links />
<_logs xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:string>String</d2p1:string>
</_logs>
<_type>String</_type>
<_warnings>
<warning>
<developerMessage>String</developerMessage>
<userMessage>String</userMessage>
</warning>
</_warnings>
<laneStatus>String</laneStatus>
</laneStatusResponse>