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 /SetSignDocumentAtributes/{ClientKey} HTTP/1.1
Host: imzagerservices.eyyubiye.bel.tr
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<SetSignDocumentAtributes xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/DaB.Imzager.Services.ServiceModel">
<Attributes xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:KeyValueOfstringstring>
<d2p1:Key>String</d2p1:Key>
<d2p1:Value>String</d2p1:Value>
</d2p1:KeyValueOfstringstring>
</Attributes>
<AuthorizationID>String</AuthorizationID>
<ClientKey>String</ClientKey>
<DocID>0</DocID>
</SetSignDocumentAtributes>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<SetSignDocumentAtributesResponse 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>
</SetSignDocumentAtributesResponse>