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 /citizen/register HTTP/1.1
Host: ws.jimsnwa.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<RegisterCitizenRQ xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Nwa.Model.Tipos.nwa.citizen">
<CreatedUser>String</CreatedUser>
<DisplayName>String</DisplayName>
<Email>String</Email>
<Id>String</Id>
<MobileId>String</MobileId>
<MobileOS>String</MobileOS>
<Password>String</Password>
<PhoneNumber>String</PhoneNumber>
<Provider>0</Provider>
<ProviderId>String</ProviderId>
</RegisterCitizenRQ>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<RegisterCitizenRS xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Nwa.Model.Tipos.nwa.citizen">
<Code xmlns="http://schemas.datacontract.org/2004/07/Nwa.Model.Tipos.nwa.core">String</Code>
<ErrorMessage xmlns="http://schemas.datacontract.org/2004/07/Nwa.Model.Tipos.nwa.core">String</ErrorMessage>
<ErrorStackTrace xmlns="http://schemas.datacontract.org/2004/07/Nwa.Model.Tipos.nwa.core">String</ErrorStackTrace>
<Data>String</Data>
</RegisterCitizenRS>