REST API

We would like to modify the content of some of the emails that are sent to the signers. As an example based on data in our application we would like to modify the content of the invitation based upon the signer being the primary person on the contract or a proxy for the person such as a legal guardian. 1) Can we modify the invitation email content, and others, via the REST API? 2) Can we modify the invitation email content per package when we create the package or prior to the invitations being sent? Thanks, Dave

We have an application that opens an overlay that contains the iframe for esigning (this is all happens in React SPA app). From what I can tell the handOver url will only redirect within the iframe containing esign. Is there anyway to have this url redirect to a parent frame instead of within the iframe ? Right now we have no way to know what's happening inside the esign iframe in our application.

Hi, I'm integrating with the e-sign live api and have had some trouble with certain pdfs causing the signing ceremony to give me a blank page. After the package is created and a url is created the window appears blank. (Even the default-consent document won't show up). Some information to hopefully help narrow it down 1) This only happens with some pdfs, others work fine 2) If I view the package using the portal, and attempt to view the pdf I uploaded (by clicking the eye..) , the blur for the overlay appears, but no pdf.

Hi There, In the integration that I'm doing, I will collect user's data on the Portal that I'm building and by using that data, I will generate a PDF and on that PDF I want to get the user's signature and the signature part has to be inside the application. For doing such integration, I don't know where to start and I couldn't find a startup guide or example for such integration in the documentation and this is my first time integrating eSignature so I'm not entirely sure on how things work as well so any guide on understanding that would be great as well. Thanks

If the signature ceremony is NOT "inperson", is there a way to specify the order in which the signers receives the doc? For example, if there are Signer A and Signer B, is there a switch to specify that Signer B should receive the package first and Signer A should wait till Signer B actually signs and only then Signer A receives the package?

We are reviewing documents we have received back from E-Sign. We have a situation where customers enter an actual written signature, and then the final document has the E-Signed By NAME HERE watermark over the actual signature. Is there any way to move or hide that watermark?

Here's the scenario. I have 2 Approvers (For example, Bob and Mary). Bob has just 1 signature field. Mary has a signature field and a Label. Bob signs first. Before Mary signs I programmatically update her Label field so when she goes to sign she sees the Label Value I inserted. Mary then signs.

I was wondering if it is possible to change the signing ceremony in the REST API after a package has been created. Example: I create a package that is set with "inPerson:false", meaning that we will not be doing the inPerson signing ceremony, rather each signer will receive an e-mail link, and then they will sign individually. We anticipate a real-life scenario where this could occur, and then the signer may wish to instead come into an agents office and sign (for whatever reason).

Hi, I have a package with status draft, Now I want to update an approval using this route PUT /packages/{packageId}/documents/{documentId} /approvals/{approvalId} Here I am updating multiple field values.

Hello, Our company operates in two separate states and will need to switch out our disclosure agreement depending on which state the application is in. What is the best way to go about this? We played around with Templates, but the number of signers can change from package to package, so that did not seem to work for us. Is there a way to have both stored on our account and have us call to a specific consent, or can we only have one consent document stored on the account? If not, I assume we will have to upload our consent document every time we create a package.