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.
GET /FavouritePinnedClientList HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/xml
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<FavouritePinnedResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<ErrorNo>0</ErrorNo>
<FavouritePins xmlns:d2p1="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">
<d2p1:FavouritePin>
<d2p1:CategoryID>0</d2p1:CategoryID>
<d2p1:ClientPinnedMarketID>0</d2p1:ClientPinnedMarketID>
<d2p1:EventTypeID>0</d2p1:EventTypeID>
<d2p1:GroupTypeCode>String</d2p1:GroupTypeCode>
</d2p1:FavouritePin>
</FavouritePins>
<Message>String</Message>
</FavouritePinnedResponse>