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/R_CellularProfiles HTTP/1.1
Host: regapi.pumpalarm.com
Content-Type: application/xml
Content-Length: length
<R_CellularProfiles xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Registrar.Model.Model.Queries">
<Ids xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:long>0</d2p1:long>
</Ids>
</R_CellularProfiles>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<ArrayOfR_CellularProfile xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Registrar.Model.Model.Data">
<R_CellularProfile>
<Description>String</Description>
<Id>0</Id>
<KoreExpressActivationProfile>String</KoreExpressActivationProfile>
<ProfileTypeId>0</ProfileTypeId>
<ServicePassword>String</ServicePassword>
<ServiceUserName>String</ServiceUserName>
<VerizonAccount>String</VerizonAccount>
<VerizonFeatureCodes>String</VerizonFeatureCodes>
<VerizonServicePlan>String</VerizonServicePlan>
<VerizonZipCode>String</VerizonZipCode>
</R_CellularProfile>
</ArrayOfR_CellularProfile>