layout | title | permalink |
---|---|---|
page |
Postback |
/postback/ |
Webhook sample to view body content
None.
By default we will send a postback when:
- There is a status change in the transaction (eg the transaction went from waiting for signer to all signed)
- There is a signer activity (eg an email was sent)
- There is a receiver activity (eg an email was sent)
A postback is sent at-least-once. There is no de-duplication. If the postback url returns a non 2xx http status code we will queue any new postbacks. In the meantime we will retry to deliver the first failed postback with an increasing interval (the first retry is within a few minutes). After 5 successive failed attempts we will send you an email. We will include the attachment with the received response (if any). When we receive a 2xx http status code we will mark the postback url as available and start sending the queued postbacks.
To verify that the postback responses are from SignHost you MUST verify our digital signature checksum. This signature is a hash of some parameters from the response and the sharedsecret. In order the generate the Checksum you will need a sharedsecret.
The checksum is generated using the following formula:
Checksum = SHA1(transaction id + || + status + | + sharedsecret)
There is a double “pipe” sign between the transaction id and the status. If you are still using our legacy API - you are seeing a File object in your postback and get responses - you'll have to include the file id at this location. eg
Checksum = SHA1(transaction id + | + file id + | + status + | + sharedsecret)
As you may have noticed the “pipe” sign ( | ) is used as the delimiter between values. You may need to put the delimiters between single quotes (‘) or double quotes (“) depending on the programming language that you will be using. The value returned by the SHA1 function is a string of 40 characters representing a hexadecimal value. How to use the SHA1 algorithm depends on your development platform. Most languages and frameworks (such as PHP and ASP.NET) have built-in implementations of the SHA1 algorithm. For other languages, such as classic ASP, implementations of the SHA1 algorithm are available online.
{
"Id": "b10ae331-af78-4e79-a39e-5b64693b6b68",
"Status": 20,
"Seal": true,
"Signers": [
{
"Id": "fa95495d-6c59-48e0-962a-a4552f8d6b85",
"Expires": null,
"Email": "user@example.com",
"Mobile": "+31612345678",
"Iban": null,
"BSN": null,
"RequireScribbleName": false,
"RequireScribble": true,
"RequireEmailVerification": true,
"RequireSmsVerification": true,
"RequireIdealVerification": false,
"RequireDigidVerification": false,
"RequireKennisnetVerification": false,
"RequireSurfnetVerification": false,
"SendSignRequest": true,
"SendSignConfirmation": null,
"SignRequestMessage": "Hello, could you please sign this document? Best regards, John Doe",
"DaysToRemind": 15,
"Language": "en-US",
"ScribbleName": "John Doe",
"ScribbleNameFixed": false,
"Reference": "Client #123",
"ReturnUrl": "http://signhost.com",
"Activities": [
{
"Id": "bcba44a9-c201-4494-9920-2c1f7baebcf0",
"Code": 103,
"Activity": "Opened",
"CreatedDateTime": "2016-06-15T23:33:04.1965465+02:00"
},
{
"Id": "de94cf6e-e1a3-4c33-93bf-2013b036daaf",
"Code": 203,
"Activity": "Signed",
"CreatedDateTime": "2016-06-15T23:38:04.1965465+02:00"
}
],
"RejectReason": null,
"SignUrl": "http://ui.signhost.com/sign/d3c93bd6-f1ce-48e7-8c9c-c2babfdd4034",
"SignedDateTime": null,
"RejectDateTime": null,
"CreatedDateTime": "2016-06-15T23:33:04.1965465+02:00",
"ModifiedDateTime": "2016-06-15T23:33:04.1965465+02:00",
"Context": null
}
],
"Receivers": [
{
"Id": "97ed6b54-b6d1-46ed-88c1-79779c3b47b1",
"Name": "John Doe",
"Email": "user@example.com",
"Language": "en-US",
"Message": "Hello, please find enclosed the digital signed document. Best regards, John Doe",
"Reference": null,
"Activities": null,
"CreatedDateTime": "2016-06-15T23:33:04.1965465+02:00",
"ModifiedDateTime": "2016-06-15T23:33:04.1965465+02:00",
"Context": null
}
],
"Reference": "Contract #123",
"PostbackUrl": "http://example.com/postback.php",
"SignRequestMode": 2,
"DaysToExpire": 30,
"SendEmailNotifications": true,
"CreatedDateTime": "2016-08-31T21:22:56.2467731+02:00",
"ModifiedDateTime": "2016-08-31T21:22:56.2467731+02:00",
"CanceledDateTime": null,
"Context": null,
"Checksum": "b5a99e1de5b9e0e9915df09d3b819be188dae900"
}