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 /zapier/v1/enquiry HTTP/1.1
Host: api.clubmanagercentral.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<ZapierEnquiryRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/ClubManager.Api.Services.Zapier">
<EmailAddress>String</EmailAddress>
<Forenames>String</Forenames>
<Message>String</Message>
<MobilePhone>String</MobilePhone>
<Surname>String</Surname>
<Tags xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:string>String</d2p1:string>
</Tags>
</ZapierEnquiryRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<ZapierEnquiryResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/ClubManager.Api.Services.Zapier">
<MemberKey>00000000-0000-0000-0000-000000000000</MemberKey>
</ZapierEnquiryResponse>