REST API

Hello, still in exploratory stages at the moment.

Hi, I'm using the REST apis. Everything is woking fine for creating packages, adding document, signature and textfields and getting the signing url. But when we mark the package as SENT, we do not want esignlive to automatically send an email to the signers. We want to handle the signing in an iFrame on our platform. Thanks Daniel

Hello all, Thank you for the good forum, and your help here! I'm trying to integrate our systems with you, and I'm sending a JSON object trying to clone a template with 1 pdf document inside, but by some reason all the fields are not listed. First thing I've noticed is that when you create the package via your website using the designer, I've noticed that in "approvals" the name field is identical with the signature field ID, and I thought that's it! But unfortunately it didn't worked!

hello, this may no be the correct forum to post this question. I've most likely overlooked this somewhere, however, where has the team published the various JSON schemas? i'd like to build some to assist with serialization/deserialization. cheers.

Hello, just started to work with the REST API. currently working thru the Python test cases / examples. i have two initial observations. 1. when i execute the test case 1 (create package) the python run output successfully completes, however, when i navigate to the dashboard i'm unable to view the draft. However, the pie graph does illustrate a numerical increment every time i run the example code. 2. test case 4 fails, suggesting the package does not exist i'm assuming both 1 and 2 are somehow directly related. cheers. run output....

Hello https://developer.esignlive.com/code-share/esignlive-rest-client-using-python/ looking at the python code, i'm trying to run one of the example application use cases. i'm simply grabbed my API key, and updated the sandbox API url parameters. from my observations, the remaining attributes (guid / doc_id / temp_id) are not required yet? any assistance and guidance would be greatly appreciated.

Once the Package is updated with status = "SENT", emails are sent to the corresponding applicants (signers) in the package. However, since this process is happening in front of the Lender, I would I like to provide the applicants (borrower) who are in front of the Lender to have access to the Signing URLS ( Assuming the borrowers are not connected or have a mobile phone which is connected to the internet). This way, I need a way for the application to retrieve all SIGNING URLS ( those URL which appears in their respective emails "Go To Document" that eSignLive send to the signers) and pres

Hi I'm trying to update the STATUS from "DRAFT" to "SENT" but getting an error. Here is my snippet...

Hi Given that a PDF can accommodate multiple Signatures where some of them may not be required , how can I format my JSON so that it does not crash? Using the sample PDF in https://developer.esignlive.com/forums/topic/simulating-rest-workflow-using-soapui/ where it is a form with a possibility of having 2 applicants - hence 2 signers. On this PDF I've therefore defined 2 possible Signature fields.

Can we send mail in cc to another user when package is send using rest api, when singer get's mail at same time cc mail goes to another email can we do that using Rest API. Thanks