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 /CustomerPreferences/ HTTP/1.1
Host: webservices.mbukdatabase.co.uk
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<CustomerPreferencesRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MBFSPreferences.ServiceModel">
<BP_ID>String</BP_ID>
<Timestamp>String</Timestamp>
<Token>String</Token>
<Username>String</Username>
</CustomerPreferencesRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<CustomerPreferencesResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MBFSPreferences.ServiceModel">
<MarketingPreference>
<MMF_Portal_Registered>false</MMF_Portal_Registered>
<OptInEmail>String</OptInEmail>
<OptInMail>String</OptInMail>
<OptInSMS>String</OptInSMS>
<OptInTelephone>String</OptInTelephone>
<TimeStamp>String</TimeStamp>
</MarketingPreference>
<ResponseStatus>
<Code>String</Code>
<Message>String</Message>
</ResponseStatus>
</CustomerPreferencesResponse>