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 /api/schedules/{id}/resend HTTP/1.1
Host: production-eros-gateway-api-supplierconnect.azurewebsites.net
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<ResendScheduleNotification xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Eros.Subtle.Dvaravartman.SupplierConnect.Model.APIModels">
<Id>00000000-0000-0000-0000-000000000000</Id>
</ResendScheduleNotification>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<ScheduleResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Eros.Subtle.Dvaravartman.SupplierConnect.Model.APIModels">
<CommunicationId>00000000-0000-0000-0000-000000000000</CommunicationId>
<Message>String</Message>
<Payload>String</Payload>
<ReferenceId>00000000-0000-0000-0000-000000000000</ReferenceId>
<Success>false</Success>
</ScheduleResponse>