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 /PopularMarketLinks HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/xml
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<PopularMarketLinksResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<Items xmlns:d2p1="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">
<d2p1:PopularMarketLink>
<d2p1:CategoryId>0</d2p1:CategoryId>
<d2p1:CategoryName>String</d2p1:CategoryName>
<d2p1:EventId>0</d2p1:EventId>
<d2p1:EventType>String</d2p1:EventType>
<d2p1:EventTypeId>0</d2p1:EventTypeId>
<d2p1:HasSameGameMulti>false</d2p1:HasSameGameMulti>
<d2p1:MasterCategoryId>0</d2p1:MasterCategoryId>
<d2p1:MasterCategoryName>String</d2p1:MasterCategoryName>
<d2p1:MasterEventId>0</d2p1:MasterEventId>
<d2p1:MasterEventName>String</d2p1:MasterEventName>
<d2p1:OrderById>0</d2p1:OrderById>
<d2p1:PopularMarketName>String</d2p1:PopularMarketName>
<d2p1:RaceNumber>0</d2p1:RaceNumber>
<d2p1:Venue>String</d2p1:Venue>
</d2p1:PopularMarketLink>
</Items>
</PopularMarketLinksResponse>