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/User/RefreshToken HTTP/1.1
Host: prod-api-auth-mb-dhc.rapp-customers.co.uk
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<RefreshUserTokenRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Mercedes.Auth.API.ServiceModel.UserSession" />
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<RefreshUserTokenResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Mercedes.Auth.API.ServiceModel.UserSession">
<Account xmlns:d2p1="http://schemas.datacontract.org/2004/07/Mercedes.Auth.API.Shared.POCO">
<d2p1:DefaultRetailerGssn>String</d2p1:DefaultRetailerGssn>
<d2p1:DefaultVehicleType>String</d2p1:DefaultVehicleType>
<d2p1:Exists>false</d2p1:Exists>
<d2p1:GasUserId>String</d2p1:GasUserId>
<d2p1:Modified>0001-01-01T00:00:00</d2p1:Modified>
<d2p1:RetailerGroupId>String</d2p1:RetailerGroupId>
<d2p1:UserId>0</d2p1:UserId>
<d2p1:UserRoleId xmlns:d3p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d3p1:int>0</d3p1:int>
</d2p1:UserRoleId>
<d2p1:UserRoleRedirectUrl>String</d2p1:UserRoleRedirectUrl>
<d2p1:UserToken>00000000-0000-0000-0000-000000000000</d2p1:UserToken>
</Account>
<IsValid>false</IsValid>
</RefreshUserTokenResponse>