REST API

I have been getting some requirements questions recently related to what our options are for customizing the look/feel of the signing ceremony.

Hello, We are in exploring REST API for creating a package with a signing document. Thanks to the good developer resources on this site, we could accomplish this part but the challenge we have is the document resides on a Cloud platform and is accessible over a URL. We had to manually copy the file locally and trigger REST API call to eSignLive. Is there an option available on eSignLive that can pull the document from a remote URL with a remoteURL parameter embedded within JSON request of package + document creation?

When a Document is signed for a given Signer, in the call back notification, I see following information "name":"DOCUMENT_SIGNED","sessionUser":"SignerID2","packageId":"XXXXXXXXXXXXXXXXXXXXXXXXX","message":null,"documentId":"Document_ID" if we see, message is coming as null. Is it possible to get some information in message? If needed, we can have that information defined in the input json, when package is being created. If we add package/transaction custom data when creating package, is it possible to get that data in notifications?

We'd like to configure an internal SMS Provider into our "on premise" eSignLive platform. The Platform Administrators guide suggests that this can be done by simply making the appropriate settings to the core.properties file. It also seems we would then need to engage this service via SOAP. Are there any other configuration steps, or considerations for setting up an internal SMS Provider solution for our eSignature on premise solution? Thanks, Todd

I want to keep track of my customer's usage for billing. Do I need another key segment or is the PackageID globally unique? My customers will have their own accounts.

Hi Haris, I would like to quickly clarify on the below approval format where I noticed that even if the page detail is not provided it works fine to realize the exact text to place the textfield using text anchor. “approvals”: [ { “role”: “signer1”, “fields”: [ { “subtype”: “CAPTURE”, “width”: 110, “binding”: null, “extract”: true, “extractAnchor”: { “text”: “desigSigner1.capture1”, “index”: 0, “width”: 100, “height”: 30, “anchorPoint”: “TOPRIGHT”, “characterIndex”: 0, “leftOffset”: 40, “topOffset”: -10 }, “l

I'm trying to add a role to an existing package in draft status.

Hello, I would like to know if there is any way to identify (without callback) delegation information and who delegates to who using REST API. I have firewall limitations that's why callback is out of the question. Regards, Felipe

Hi, There is a confusion when we use the callback function, is there anyone to give some advice? The callback url is based on our application. And this path is correct when running directly in the browser, however there is no reaction after the callback event action. How could I research this issue and is there any way to resolve it ? Thanks in advance.

Hi, I have 3 forms. Each form has Signature Capture Fields Example SignerId1.Capture1, SignerId2.Capture2, [ExtraSignerId1.Capture1],[ExtraSignerId2.Capture2]...etc When I print the form individually as 3 packages, it is created and email is triggered to complete the signature ceremony. However, when I bundle the 3 PDF together ( via a 3rd party tool in my application ), it creates 1 PDF combining all 3 forms with their respective Signature Capture fields.