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 /SignDocumentPDFV2 HTTP/1.1
Host: imzagerservices.eyyubiye.bel.tr
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<SignDocumentPDFV2 xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/DaB.Imzager.Services.ServiceModel">
<AuthorizationID>String</AuthorizationID>
<ClientKey>String</ClientKey>
<DocumentId>0</DocumentId>
<Location>0</Location>
<Message>String</Message>
<SigningLocation>String</SigningLocation>
<SigningReason>String</SigningReason>
<UserSSN>String</UserSSN>
</SignDocumentPDFV2>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<SignDocumentPDFResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/DaB.Imzager.Services.ServiceModel">
<ErrorMesage>String</ErrorMesage>
<Result>false</Result>
<ServiceSuccessResult>false</ServiceSuccessResult>
</SignDocumentPDFResponse>