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_accountlist HTTP/1.1
Host: sdk.lovettcommercial.com
Content-Type: application/xml
Content-Length: length
<post_event_payment_accountlist xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.postevent">
<email>String</email>
<idcia>0</idcia>
<pageIndex>0</pageIndex>
<pageSize>0</pageSize>
<search>String</search>
<token>String</token>
<tokensecret>String</tokensecret>
</post_event_payment_accountlist>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<post_event_payment_accountlistResponse 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>
<eventAccount>
<costcode>false</costcode>
<dbtcrd>String</dbtcrd>
<idledger>String</idledger>
<ledger>String</ledger>
<level>String</level>
<name>String</name>
</eventAccount>
</list>
</post_event_payment_accountlistResponse>