Blog: Developer

Developer Community: Week In Review – June 5, 2017

week in review

Let’s take a quick look at some of the questions that have been asked during the week of June 5th in the Developer Community.

Send Package/Transaction Without Signatures

In order to process a transaction in eSignLive, the minimum requirements are the following:

  • One signer
  • One document (not including the default-consent)
  • One signature

Therefore, you cannot simply send a document without any signatures to a recipient.

Link To Community Forums Post

Transaction Ready To Complete

If you need to review the transaction and its documents before marking it complete, you can turn off the auto-complete setting. When you are ready to complete the transaction, you can do so programmatically through the SDKs/API:

Java SDK

eslClient.getPackageService().markComplete(packageId);

.NET SDK

eslClient.PackageService.MarkComplete(packageId);

REST API

PUT https://sandbox.esignlive.com/api/packages/{packageId}

{
   "status": "COMPLETED"
}

Link To Community Forums Post

Signing URL vs. Session Tokens

The signing URL is the same URL as in the email notification you receive to sign documents. When accessing a package using the signing URL, the application assumes you are remote. Therefore, if you have set any authentication (SMS/Q&A), it will be enabled. Finally, the signing URL does not expire. The signer can always access the package so long as the package isn’t in draft.

As for session tokens, they expire after 30 mins and can be used multiple times within that time frame. However, if you’ve set any authentication (SMS/Q&A), it will be bypassed. To create a signing session using signer authentication tokens, you’ll need to do the following:

Java SDK

String signerAuthToken = eslClient.getAuthenticationTokenService().createSignerAuthenticationToken(packageId, signerId);

.NET SDK

string signerAuthToken = eslClient.AuthenticationTokenService.CreateSignerAuthenticationToken(packageId, signerId);

REST API

POST https://sandbox.esignlive.com/api/authenticationTokens/signer/multiUse

{
   "packageId": "{packageId}",
   "signerId": "{signerId}"
}

And build the following url:

https://sandbox.esignlive.com/access?sessionToken={signerAuthenticationToken}

Link To Community Forums 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. You can find all of my previous blogs by going to my author page.

Haris Haidary
Junior Technical Evangelist
LinkedIn | Twitter

eSignLive Developer Community!

Join the eSignLive Developer Community!
Forums, blogs, documentation, SDK downloads and more.

Join Today
@eSignLive Week In Review in the Developer Community 06/05/2017 http://bit.ly/2rrOEvn#esignlive #developer #community Click to tweet

Leave a Reply