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 /ContentfulFeaturedEventRacing HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/xml
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<ContentfulFeaturedEventRacingResponse 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>
<ContentfulFeaturedEvent xmlns:d2p1="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.ApiModels">
<d2p1:ContentfulFeaturedEvent>
<d2p1:EventID>0</d2p1:EventID>
<d2p1:EventName>String</d2p1:EventName>
<d2p1:EventOrder>0</d2p1:EventOrder>
<d2p1:PromotionDetail>String</d2p1:PromotionDetail>
<d2p1:PromotionTitle>String</d2p1:PromotionTitle>
</d2p1:ContentfulFeaturedEvent>
</ContentfulFeaturedEvent>
</ContentfulFeaturedEventRacingResponse>