ImzagerServices

<back to all web services

SignDocumentPDFV2

The following routes are available for this service:
All Verbs/SignDocumentPDFV2
SignDocumentPDFV2 Parameters:
NameParameterData TypeRequiredDescription
ClientKeyquerystringNo
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 .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

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/json
Content-Type: application/json
Content-Length: length

{"ClientKey":"String","AuthorizationID":"String","UserSSN":"String","DocumentId":0,"Message":"String","SigningReason":"String","Location":0,"SigningLocation":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Result":false,"ServiceSuccessResult":false,"ErrorMesage":"String"}