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_event_payment_vendorlist HTTP/1.1
Host: sdk.lovettcommercial.com
Content-Type: application/xml
Content-Length: length
<post_event_payment_vendorlist xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.postevent">
<email>String</email>
<token>String</token>
<tokensecret>String</tokensecret>
</post_event_payment_vendorlist>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<post_event_payment_vendorlistResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.postevent">
<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>
<eventVendor>
<contactname>String</contactname>
<disapply>String</disapply>
<dueterm>String</dueterm>
<eb380>false</eb380>
<email>String</email>
<fox2>String</fox2>
<idvendor>String</idvendor>
<invoiceyn>false</invoiceyn>
<list>
<venderCostCode>
<ledger>String</ledger>
<name>String</name>
</venderCostCode>
</list>
<phone1>String</phone1>
<taxrate>0</taxrate>
<termino>String</termino>
<vendorname>String</vendorname>
<vtype>String</vtype>
</eventVendor>
</list>
</post_event_payment_vendorlistResponse>