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/post_next_ach_withdraw HTTP/1.1
Host: sdk.lovettcommercial.com
Content-Type: application/xml
Content-Length: length
<post_next_ach_withdraw xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.scheduleChecklist">
<email>String</email>
<idtenant>String</idtenant>
<token>String</token>
<tokensecret>String</tokensecret>
</post_next_ach_withdraw>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<post_next_ach_withdrawResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.scheduleChecklist">
<message xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post">String</message>
<result xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post">0</result>
<ccpercentage>String</ccpercentage>
<datefrom>0001-01-01T00:00:00</datefrom>
<dateto>0001-01-01T00:00:00</dateto>
<lovett>String</lovett>
<maxdate>0001-01-01T00:00:00</maxdate>
<premisesf>String</premisesf>
<totalsales>String</totalsales>
</post_next_ach_withdrawResponse>