Today, alongside our latest eSignature API release, we are pushing three new example applications live. These examples cover some common use cases so you can see the API in action. Included with each example are code samples to help you build test applications of your own. All 3 of these you can try live within our API documentation.
2-Factor Authentication Using Twilio and HelloSign
HelloSign already authenticates user identity via email verification. However, if you are looking for an additional level of security you can add 2-factor identification to a document. This example uses the Twilio API to send an access code by SMS as well as HelloSign’s standard email verification. You programmatically set the access code while creating the signature request. Then the Twilio and HelloSign APIs take care of the rest!
Sending a Document based on User Action
Forget having your users leave a digital workflow just to sign a document. This example shows how to have a user action trigger a signature request for improved digital workflow automation. In this example a signature request for a Contributor License Agreement (CLA) is sent after a user submits code to an open source project on GitHub. This is done with an integration between the GitHub pull request webhook and the HelloSign API.
Embedded Signing creates a seamless user experience inside a workflow on your own site. The advantage is users won’t need to leave your site to complete an eSignature. This creates improved flows and a better user experience which leads to higher conversion rates. In this example you get to experience embedded signing form the perspective of a site visitor as you are asked to sign a document.
In the coming weeks we will be releasing more eSignature API example apps and would love to hear what projects you are working on. Please share your ideas here.