REST API

Does the signing url support authentication using SAML or some other means so that if someone gets access to the URL they wouldn't be able to use it without a valid token?

Hi, I'm working to retrieve all sender from the accounts that I manage in order to generate some reports. I'm trying to figure out what is the best approach to incrementally grab new senders without retrieving the full list again. Do you have any suggestion using REST API's calls? I'm trying to use SORT by created, but the results still take into consideration the sender status. Regards, Felipe

Hi Team I would like to sign all the documents on behalf of sender and multiple signer using a package id. I don't want to go through the each signer using eslClient.signDocuments(packageId, "Client1") (bulk signing for a signer) ; is it possible to implement eslClient.signDocuments(packageId) in Rest API . Thanks for the help.

At my work place, we are trying to get a Sender Authentication token for a package using the below information /api/authenticationTokens/sender Authorization and Accept Headers are included. In Body, in the request payload, inlcuded packageId in JSON. Getting below error { "code": 404, "message": "The requested resource does not exist on this server.", "messageKey": "error.routeNotFound", "name": "Resource Not Found", "technical": "This route does not exist." } we are on version 11.0.4 I believe. Any inputs on how to make this work? Does this Sender token, depend

Hi, does the URL given by https://sandbox.esignlive.com/api/packages/{id}/roles/{id}/signingUrl expire? If so, is it configurable? Thanks, Jimmy

Hi Team, We are using rest API to communicate with esign live . when we create and send document we are using the below url . https://sandbox.e-signlive.com/api/packages Once we send the request I am able to see the package in drafts folder . I am not receiving the mail also . I would like to have the package in inbox and not in drafts folder .Could you please guide me on this . Thanks for the help.

When I do PUT request to /api/packages/{package_id} with request payload as { "status": "DRAFT" } I get error response as { "code": 415, "entity": null, "message": "Unsupported Media Type", "messageKey": "http.status.415", "name": "Unsupported Media Type", "technical": "", "packageId": null } I have included Authorization and Accept headers in the request and above payload in Body. I am able to verify that package id is valid, and its current status is SENT. Verified by doing GET request via REST API. What are all the list of status for a package?

Apart from the feature guides, where can I find the complete documentation for all the REST API features available? In some cases, I found different examples, and the URI was different.

So I was able to create a package, with a field which is placed on the first page. How can I say that the field needs to be on every page?, or only on the last page, keeping in mind that I don't know in front how many pages the file contains ?

We've done our initial production rollout of our new feature that includes eSignLive integration - everything is working great, but one of the early feedback items that has come back our way is the desire to do a bit of custom branding around the signing session. One of the items requested was to place our custom logo on the top left of the signing session - this was very easy to accomplish via the API (settings -> ceremony -> layout -> brandingBar -> logo), but I believe there is also a way to customize the look and feel of the "Thank You" dialog, correct? There is documentation