Week In Review: Developer Community - April 3, 2017
Let's take a quick look at what happened for the week of April 3rd in the Developer Community.
Enforce Capture Signature
With the latest release of eSignLive, a new capture-signature feature at the transaction level has been implemented. If this feature is enabled, recipients must capture their signature every time they sign. Otherwise, the signature is captured only once, and then applied to all subsequent signatures, for which the recipients clicks to sign. Link to Post
DOCUMENT_SIGNED Callback Notification
If you have been using Callback Event Notifications, you most likely noticed the "sessionUser" field that is included in the JSON payload when an event is triggered. The "sessionUser" field returns you the signer id. With this, you should be able to grab the package JSON and identify the recipient using this id. From there, you will be able to grab their information, such as the email address. Link to Post
Create Signing Session
With eSignLive, you have the ability to embed the signing experience in your application using an iframe. The URL you will be looking to build is the following:
https://sandbox.esignlive.com/access?sessionToken={signerAuthenticationToken}
In addition, you can also download the signed PDF documents through our API. You can find how to do both from the link below. Link to Post If you have questions regarding this blog or anything else concerning integrating eSignLive into your application, visit the Developer Community Forums: developer.esignlive.com. That's it from me. Thank you for reading! If you found this post helpful, please share it on Facebook, Twitter, or LinkedIn.
Haris Haidary Junior Technical Evangelist LinkedIn | Twitter
