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 /CheckAndUpdateClientInfoDraftGreenIdVerificationStatus HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<CheckAndUpdateClientInfoDraftGreenIdVerificationStatusRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<AccountId>String</AccountId>
<Password>String</Password>
<ReferenceCode>String</ReferenceCode>
<RequestUrl>String</RequestUrl>
<VerificationToken>String</VerificationToken>
</CheckAndUpdateClientInfoDraftGreenIdVerificationStatusRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<CheckAndUpdateClientInfoDraftGreenIdVerificationStatusResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<ErrorNo xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">0</ErrorNo>
<Identity xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">0</Identity>
<Message xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">String</Message>
<FinalVerificationStatus>String</FinalVerificationStatus>
</CheckAndUpdateClientInfoDraftGreenIdVerificationStatusResponse>