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 /service/CalendarNotification/{username} HTTP/1.1
Host: www.bernhardthospitality.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<CalendarNotification xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Cronofy">
<channel>
<callback_url>String</callback_url>
<channel_id>String</channel_id>
<filters>
<calendar_ids xmlns:d4p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d4p1:string>String</d4p1:string>
</calendar_ids>
<only_managed>false</only_managed>
</filters>
</channel>
<notification>
<changes_since>0001-01-01T00:00:00</changes_since>
<type>String</type>
</notification>
<username>String</username>
</CalendarNotification>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<NotificationReceived xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Cronofy">
<channel>
<callback_url>String</callback_url>
<channel_id>String</channel_id>
<filters>
<calendar_ids xmlns:d4p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d4p1:string>String</d4p1:string>
</calendar_ids>
<only_managed>false</only_managed>
</filters>
</channel>
<notification>
<changes_since>0001-01-01T00:00:00</changes_since>
<type>String</type>
</notification>
<username>String</username>
</NotificationReceived>