Let’s take a quick look at what happened for the week of June 26th in the eSignLive Developer Community.
Across transactions in eSignLive, the only id that is unique is the package id, which is automatically generated during transaction creation. As for role ids, you can reuse them across your transactions. You could use, for example, Signer1 and Signer2 in all of your transactions. They only need to be unique within a transaction so that their approvals (signatures and fields) can be tied to their particular roleId.
Session Users in Callback Event Notifications
When using callback event notifications, eSignLive returns you a sessionUser field in the json payload. The sessionUser lines up with the signer id. If you haven’t set a custom signer id, eSignLive will automatically generate one for you and you will receive this information in the sessionUser field.
Is an Email Required for In-Person Signing?
An email address is always required for adding a signer in eSignLive. In fact, the minimum that is required for adding a signer are: first name, last name, and email address. This is also the case when doing an in-person signing. Also, when creating an in-person signing session, you do not need to get a signer token for each signer. You can simply get one for one signer and you will have the ability to switch between signers in the same session using the drop-down that will be available to you.
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. You can find all of my previous blogs by going to my author page.