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_maintenance_schedule2_list HTTP/1.1
Host: sdk.lovettcommercial.com
Content-Type: application/xml
Content-Length: length
<post_maintenance_schedule2_list xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.scheduleChecklist">
<email>String</email>
<endDate>String</endDate>
<idtenant>0</idtenant>
<startDate>String</startDate>
<token>String</token>
<tokensecret>String</tokensecret>
</post_maintenance_schedule2_list>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<post_maintenance_schedule2_listResponse 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>
<list>
<maintenance_schedule2_list>
<description>String</description>
<finishDate>0001-01-01T00:00:00</finishDate>
<finishby>String</finishby>
<idnumber>String</idnumber>
</maintenance_schedule2_list>
</list>
</post_maintenance_schedule2_listResponse>