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 /phoneverification/verification/{RequestId}/{Code} HTTP/1.1
Host: stubbur-autoupdates-live.smartnewapis.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<ConfirmPhoneVerificationRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<Code>String</Code>
<Path>String</Path>
<RequestId>String</RequestId>
<RequestUnixUTCTimeStamp>0</RequestUnixUTCTimeStamp>
<SenderVerification>String</SenderVerification>
<Signature>
<Signature>String</Signature>
<SystemId>String</SystemId>
<SystemSecret>String</SystemSecret>
</Signature>
</ConfirmPhoneVerificationRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<PhoneVerificationResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<CodeMatches>false</CodeMatches>
<StatusCode>0</StatusCode>
<StatusMessage>String</StatusMessage>
<Token>String</Token>
</PhoneVerificationResult>