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.
PUT /PutEmailAddress_RegRequestDate/ HTTP/1.1
Host: webservices.mbukdatabase.co.uk
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<PutEmailAdd_RegRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MBMMFAutoEnrol.ServiceInterface.Services.PutEmailAdd_RegRequestDate">
<BPID>0</BPID>
<EmailAddress>String</EmailAddress>
</PutEmailAdd_RegRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<PutEmailAdd_RegResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MBMMFAutoEnrol.ServiceInterface.Services.PutEmailAdd_RegRequestDate">
<AlreadyRegistered>false</AlreadyRegistered>
<Error>String</Error>
<Success>false</Success>
</PutEmailAdd_RegResponse>