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_ach_draw_list HTTP/1.1
Host: sdk.lovettcommercial.com
Content-Type: application/xml
Content-Length: length
<post_ach_draw_list xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.ACH">
<email>String</email>
<idcia>String</idcia>
<idtenant1>String</idtenant1>
<token>String</token>
<tokensecret>String</tokensecret>
</post_ach_draw_list>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<post_ach_draw_listResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.ACH">
<message xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post">String</message>
<result xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post">0</result>
<list>
<post_ach_draw_info>
<amountdue>String</amountdue>
<duedate>0001-01-01T00:00:00</duedate>
<idnumber>String</idnumber>
<ncustomer>String</ncustomer>
<reason>String</reason>
<refnumber>String</refnumber>
<xselect>String</xselect>
</post_ach_draw_info>
</list>
</post_ach_draw_listResponse>