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/getAgingReportList HTTP/1.1
Host: app.lovettcommercial.com
Content-Type: application/xml
Content-Length: length
<getAgingReportList xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/LovettCommercialService">
<date>String</date>
<email>String</email>
<token>String</token>
<tokensecret>String</tokensecret>
</getAgingReportList>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<AppResponse.getAgingReportList xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/LovettCommercialService">
<_x003C_agingReport_x003E_k__BackingField>
<AppResponse.getAgingReport>
<_x003C_ciaid_x003E_k__BackingField>String</_x003C_ciaid_x003E_k__BackingField>
<_x003C_cianame_x003E_k__BackingField>String</_x003C_cianame_x003E_k__BackingField>
<_x003C_p1_x003E_k__BackingField>String</_x003C_p1_x003E_k__BackingField>
<_x003C_p2_x003E_k__BackingField>String</_x003C_p2_x003E_k__BackingField>
<_x003C_p3_x003E_k__BackingField>String</_x003C_p3_x003E_k__BackingField>
<_x003C_p4_x003E_k__BackingField>String</_x003C_p4_x003E_k__BackingField>
<_x003C_p5_x003E_k__BackingField>String</_x003C_p5_x003E_k__BackingField>
<_x003C_p6_x003E_k__BackingField>String</_x003C_p6_x003E_k__BackingField>
<_x003C_xxyy_x003E_k__BackingField>String</_x003C_xxyy_x003E_k__BackingField>
</AppResponse.getAgingReport>
</_x003C_agingReport_x003E_k__BackingField>
<_x003C_existyn_x003E_k__BackingField>String</_x003C_existyn_x003E_k__BackingField>
<_x003C_found_x003E_k__BackingField>String</_x003C_found_x003E_k__BackingField>
<_x003C_validtoken_x003E_k__BackingField>String</_x003C_validtoken_x003E_k__BackingField>
</AppResponse.getAgingReportList>