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 /Account/SetupNotary HTTP/1.1
Host: api.securedsigning.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<NotarySetupRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/SecuredSigning.Api.Rest.Requests">
<CommissionExpiry>String</CommissionExpiry>
<CommissionId>String</CommissionId>
<County>String</County>
<EnableCertificate>false</EnableCertificate>
<EnableIpen>false</EnableIpen>
<EnableNotary>false</EnableNotary>
<EnableOnlineAct>false</EnableOnlineAct>
<EnableRon>false</EnableRon>
<NotarySignature>String</NotarySignature>
<NotaryStamp>String</NotaryStamp>
<OnlineAct>String</OnlineAct>
<State>String</State>
</NotarySetupRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<NotaryCheck xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/SecuredSigning.Api.Rest.Models">
<CertificateEnabled>false</CertificateEnabled>
<CertificateExpiry>String</CertificateExpiry>
<CommissionExpiry>String</CommissionExpiry>
<CommissionId>String</CommissionId>
<County>String</County>
<IpenEnabled>false</IpenEnabled>
<NotaryEnabled>false</NotaryEnabled>
<OnlineAct>String</OnlineAct>
<OnlineActEnabled>false</OnlineActEnabled>
<RonEnabled>false</RonEnabled>
<State>String</State>
</NotaryCheck>