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 /v1/UpdateAgencyMulesoftQueueState HTTP/1.1
Host: prod-api-agency-orch-mb-dhc.rapp-customers.co.uk
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<UpdateAgencyMulesoftQueueState xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Mercedes.Agency.Orchestration.API.ServiceModel.MulesoftLambdaQueue">
<DisabledReason xmlns="http://schemas.datacontract.org/2004/07/Mercedes.Agency.API.Shared.POCO.AgencyMulesoftQueue">String</DisabledReason>
<GasId xmlns="http://schemas.datacontract.org/2004/07/Mercedes.Agency.API.Shared.POCO.AgencyMulesoftQueue">String</GasId>
<StatusChanged xmlns="http://schemas.datacontract.org/2004/07/Mercedes.Agency.API.Shared.POCO.AgencyMulesoftQueue">Enabled</StatusChanged>
</UpdateAgencyMulesoftQueueState>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<UpdateAgencyMulesoftQueueStateResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Mercedes.Agency.API.Shared.POCO.AgencyMulesoftQueue">
<LastModified>String</LastModified>
<MessageCount>0</MessageCount>
<Status>false</Status>
</UpdateAgencyMulesoftQueueStateResponse>