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_ticketList HTTP/1.1
Host: ssl.buildersaccess.com
Content-Type: application/xml
Content-Length: length
<post_ticketList xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK.post.Request">
<email>String</email>
<idtenant>String</idtenant>
<token>String</token>
<tokensecret>String</tokensecret>
</post_ticketList>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<post_ticketListResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK.post.Request">
<list>
<TicketInfo>
<acknowledgedate>0001-01-01T00:00:00</acknowledgedate>
<address>String</address>
<archivedate>0001-01-01T00:00:00</archivedate>
<assignpm>String</assignpm>
<category>
<category>String</category>
<description>String</description>
<idnumber>String</idnumber>
</category>
<creadate>0001-01-01T00:00:00</creadate>
<description>String</description>
<followup>String</followup>
<idcia>String</idcia>
<idproject>String</idproject>
<idtenant>String</idtenant>
<idticket>String</idticket>
<idwebcare1>String</idwebcare1>
<list>
<attachmentFile>
<base64>String</base64>
<base64Thumbnail>String</base64Thumbnail>
<fileName>String</fileName>
</attachmentFile>
</list>
<location>String</location>
<priority>String</priority>
<status>String</status>
<tenantname>String</tenantname>
<username>String</username>
</TicketInfo>
</list>
<message>String</message>
<result>0</result>
</post_ticketListResponse>