ImzagerServices

<back to all web services

SignDocumentPDF

The following routes are available for this service:
All Verbs/SignDocumentPDF/{ClientKey}
SignDocumentPDF Parameters:
NameParameterData TypeRequiredDescription
ClientKeypathstringNo
AuthorizationIDquerystringNo
UserSSNquerystringNo
DocumentIdquerylongNo
MessagequerystringNo
SigningReasonquerystringNo
LocationqueryintNo
SigningLocationquerystringNo
SignDocumentPDFResponse Parameters:
NameParameterData TypeRequiredDescription
ResultformboolNo
ServiceSuccessResultformboolNo
ErrorMesageformstringNo

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 /SignDocumentPDF/{ClientKey} HTTP/1.1 
Host: imzagerservices.eyyubiye.bel.tr 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<SignDocumentPDF 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>
</SignDocumentPDF>
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>