Let’s take a quick look at what happened for the week of May 22nd in the Developer Community.
When retrieving packages through our REST API (e.g.
GET https://sandbox.esignlive.com/api/packages), you may have noticed that only the latest updated package is returned to you, along with a count. To retrieve more than one package, you will need to add the parameters “from” and “to” in your request URL (e.g.
GET https://sandbox.esignlive.com/api/packages?from=0&to=99). These parameters specify the number of packages returned to you for the purposes of pagination. It is important to note that a maximum of 100 packages can be returned per request.
For a complete list of parameters available, you can head over to our API documentation.
Signing Programmatically Through The API
With the release of eSignLive 11, the Sign All feature was introduced. Essentially, this API/SDK call enables all documents in a transaction to be signed in one call (instead of traversing documents successively, and signing each signature successively). The process is relatively straight forward using the Java or .NET SDK (a one liner). However, if you’re looking to programmatically sign through the REST API, the process requires a few steps. You can have a look the following guide for a step-by-step instruction on how to Sign All through the REST API.
With each package/transaction you create in eSignLive, you have the ability to add a Reviewer. As the name suggests, a Reviewer’s task is to review each transaction. Hence, he or she is not assigned any signatures on any document in the transaction. Also, a Reviewer can access the transaction anytime to review it by either clicking the link in the email notification or having a session created through your web application. To add a Reviewer in a transaction, simply add a signer but don’t add any signatures for this particular “signer”. He or she will be your Reviewer 🙂 .
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.