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 /VenueSeriesTicketTypeConnections HTTP/1.1
Host: stubbur-autoupdates-live.smartnewapis.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<VenueSeriesTicketTypeConnectionSearchRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<OwnerId>0</OwnerId>
<SectionId>0</SectionId>
<TicketTypeId>0</TicketTypeId>
<VenueId>0</VenueId>
</VenueSeriesTicketTypeConnectionSearchRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<VenueSeriesTicketTypeConnectionSearchResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<Items xmlns:d2p1="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel.Types">
<d2p1:VenueSeriesTicketTypeConnection>
<d2p1:ID>0</d2p1:ID>
<d2p1:MaxTickets>0</d2p1:MaxTickets>
<d2p1:SeriesTicketId>0</d2p1:SeriesTicketId>
<d2p1:VenueId>0</d2p1:VenueId>
<d2p1:VenueSeatingSectionId>0</d2p1:VenueSeatingSectionId>
</d2p1:VenueSeriesTicketTypeConnection>
</Items>
<Message>String</Message>
<StatusCode>0</StatusCode>
</VenueSeriesTicketTypeConnectionSearchResult>