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/sch_pmSubmitPreConstructionList HTTP/1.1
Host: ssl.buildersaccess.com
Content-Type: application/xml
Content-Length: length
<sch_pmSubmitPreConstructionList xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<idcia>String</idcia>
<idproject>String</idproject>
<list>
<PreconstructionItem>
<idtemplate>String</idtemplate>
<item>String</item>
<title>String</title>
</PreconstructionItem>
</list>
<token>String</token>
<tokensecret>String</tokensecret>
</sch_pmSubmitPreConstructionList>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<AppResponse.Sch_Returndata xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BASchedulingSDK">
<_x003C_found_x003E_k__BackingField>String</_x003C_found_x003E_k__BackingField>
<_x003C_message_x003E_k__BackingField>String</_x003C_message_x003E_k__BackingField>
<_x003C_validtoken_x003E_k__BackingField>String</_x003C_validtoken_x003E_k__BackingField>
</AppResponse.Sch_Returndata>