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 /event HTTP/1.1
Host: devapi.billhighway.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<CreateUpdateEvent xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BH.CloudAPI.Common4.DTO.SalesForce">
<ClassName>String</ClassName>
<ClientId>0</ClientId>
<CostCenter>String</CostCenter>
<CreatedDateTime>0001-01-01T00:00:00</CreatedDateTime>
<EventDescription>String</EventDescription>
<EventName>String</EventName>
<GroupId>String</GroupId>
<Region>String</Region>
<RegionCostCenter>String</RegionCostCenter>
<UniqueId>String</UniqueId>
</CreateUpdateEvent>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<CreateUpdateEventReply xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BH.CloudAPI.Common4.DTO.SalesForce">
<BillhighwaycampaignId>String</BillhighwaycampaignId>
<ClassName>String</ClassName>
<ClientId>0</ClientId>
<CreatedDateTime>0001-01-01T00:00:00</CreatedDateTime>
<ErrorCode>0</ErrorCode>
<ErrorMessage>String</ErrorMessage>
<UniqueId>String</UniqueId>
</CreateUpdateEventReply>