REST API

I'm currently using the sandbox version of eSignlive and I wish to configure the designer view (hide various elements). I found this page which says "To modify your designer settings, you first need to have a designer settings profile enabled on your account. Please contact your administrator for help. ". Could I get some more information regarding who to contact in order to access the designer settings?

Hi guys, I looked around and am not able to find confirming on this: is it possible to embed the form/package for user to sign on our website? All of our users have their own account and it would be nice to be able to display the form directly in their account. Let me know as soon as you get a chance. Thanks!

I use the package creation document upload API to create a document for signature. I want to make sure our signers receive a signed copy of their document at the end of signing. How can I assure that the signed document (other than the disclosure) is attached to the success email at conclusion. Thanks

I would like to show my signer a message that says something to the effect of: “Thank you for signing your application. We will send you a completed copy of the application signed by both you and the vender.” This would be something like an alert upon completed signature.

I have a document that is newly uploaded and created on the fly. What is the best way to place the signature fields within the PDF? Is this a separate REST API call?

I have a document that is generated on the fly by our web system. It's a PDF created by the back-end and then goes out for signing. I have been able to upload the document just fine. Once it goes out for signing, there are two signatures it requires. One is from the vendor and the other from the customer. I want a way to store the vendor signature so it's always just 'automatically signed' by them. This makes it so the only signature needed is that of the customer in question. What is the best way to go about this process via the REST API?

I will have a great number of users to maintain. In order to simplify process and to make adding and modifying users I need to (or prefer to) 1. Add users programmatically (this probably has to return user API key) 2. Once user is added I would need to modify a. Callback URL b. Callback Key c. Select events Is this possible to achieve and how?

I'm using the POST /packages/{packageId}/clone API call to create package from template. The template has some fields added and I want to fill one of them so the signer will not be able to change it. Is it possible? And if yes, what parameters I need to pass in JSON payload to do so?

Hi! Do you have anywhere online full REST API documentation with all possible request payload fields defined? For example, there is a http://docs.e-signlive.com/doku.php?id=esl:api:e-signlive_templates#post_packages_packageid_clone (POST /packages/{packageId}/clone) but the list of fields is very basic. I found https://ww

Hi Team, We are trying to create the Approvals using REST API. This works without any issues when we don't use the text anchors. However, when we use text anchors, we don't get the expected results i.e. the approval fields are created taking the field attributes in to consideration, ignoring the extractAnchor values. We saw that "Warning: Text anchor extraction cannot be used in this API call." when creating the approvals.