To override the Content-type in your clients, use the HTTP Accept Header, append the .soap11 suffix or ?format=soap11
HTTP + SOAP11
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /soap11 HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: MigratedBetHistoryRequest
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<MigratedBetHistoryRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<ClientId>0</ClientId>
<Migration>String</Migration>
</MigratedBetHistoryRequest>
</soap:Body>
</soap:Envelope>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<MigratedBetHistoryResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<CSVBetHistory>String</CSVBetHistory>
</MigratedBetHistoryResponse>
</soap:Body>
</soap:Envelope>