With Docubee API, integrating secure and legally binding eSignatures into your native applications has never been easier. Whether you wish to send singers an email or have them access documents using a link or QR code, we’ve got you covered. Continue reading for more information on using eSignature requests in Docubee.
The Docubee API provides support for integrating eSignature requests in two ways. The first is to have Docubee handle sending an email to the signers directly and managing the signing ceremony within the platform. The second is to have the API return a link that can be integrated into your solution, which can be displayed in many ways such as a button that launches the signature ceremony or perhaps for more seamless integration in your platform via an iframe.
Creating a Link for Signing with Docubee API
For this first example, let’s take a look at creating a link for signing (however, you can also mix both links and emails if it better suits your needs).
1. To start the process we must upload the document we wish to have signed.
Use this code for your document upload:
Curl: https://gist.github.com/ontask-gist/aeb11dbc47f27cb225dcdc75e0efdf34.js
Node.js: https://gist.github.com/ontask-gist/a3a98d3197b374e520c6eae58f40cb5c.js
Python: https://gist.github.com/ontask-gist/8f1b81aa490b1138edb23eafc9621dcb.js
2. Once successful the API will respond with a documentId we will use in the next step.
3. The next request will contain a list of users and the method you wish to have them sign. It will also contain a list of users who will receive the final document once completed. To review the full list of options please refer to our documentation.
Generating a Signing Link with Docubee API
In this example, Docubee will generate a hyperlink using “link” as the type for a signer that you can then use in your application. If you’re interested in using Docubee to manage emails check out our other walkthrough here.
Curl: https://gist.github.com/ontask-gist/7512663c7869632fbb8481e6cf6fe480.js
Node.js: https://gist.github.com/ontask-gist/38432f8d4f1644c24135f826b21255b4.js
Python: https://gist.github.com/ontask-gist/380d9cea72cf8f2fd31f9b5f03543ffb.js
The API will respond with information about each of the signers as well as a processId which can be used to retrieve the status of the signature ceremony as needed.
<partial api response with processId>
https://gist.github.com/ontask-gist/24f19ebe472f5d940f5f3596f90a9049.js
Checking Signature Status
The request to check the status of your signatures would then look like the following:
<code for status>
Curl: https://gist.github.com/ontask-gist/1cd7e945db3b6414d7bb9674c842c7f5.js
Node.js: https://gist.github.com/ontask-gist/413597db35b2612716bc54cfd0a0fee0.js
Python: https://gist.github.com/ontask-gist/1a9cff60db9cb84557daf146389fe30b.js
Once complete, the final document will automatically be sent to the users identified in the onSignaturesFinalized property when you started the signature request above. If no users were declared the final document can be retrieved using our Download a Document endpoint.
Get Documents Signed Faster with Docubee API
If you need to get documents signed, we have the tools you need for success. It’s time to make the process easier for everyone involved. You can learn more about the extensive features of Docubee’s eSignature API in our documentation.
