REST API

While attempting to upload a document to a package via the following call:

https://sandbox.esignlive.ca/api/packages/9uPhYzkvKRJXmdxv4Bje_7gz9Ls=/documents 

I am presented with the following error:

POST https://sandbox.e-signlive.ca/api/packages/9uPhYzkvKRJXmdxv4Bje_7gz9Ls=/documentsresulted in a500 Internal Server Error` response:
{"code":500,"messageKey":"error.internal.default","technical":"name cannot be null or empty","message":"Unexpected error

I did manage to view the entire body of the error message and it was a generic default error message.

Hi I have a working sample with Document Extraction using the eSignlive signature Field in [] and I'm converting it to using Position Extraction , using regular Field Name in the PDF and using the same JSON payload. However, I cannot get the ESL to recognize the Signature Fields under Position Extraction . do you have an example of using Position Extraction with REST? Or point out the main key attributes which is responsible in defining the SIgnature Controls for the Roles in the JSON?

int the call to CreatePackage when calling the eSign rest api , we get 500 error from the server. EslServerException: The remote server returned an error: (500) Internal Server Error. HTTP POST on URI https://sandbox.e-signlive.ca/api/packages/o6Qqzj2LSQVcL28SnOxjUNKx-oE=/documents. Optional details: {"code":500,"messageKey":"error.internal.default","technical":"name cannot be null or empty","message":"Unexpected error. I have attached a JSON dump of the request to the eSign api. Any thoughts? thx.

Hi I want to Specify/ restrrict the Documents a Recipient Can View. The following link has java and C#code https://docs.esignlive.com/content/c_integrator_s_guide/sdk/c_managing_documents/document_visibility.htm?Highlight=document%20visibility%20#Specifyi It seems that there is an account level setting as well , that needs to be enabled. Following is the java code .

I always get this error while trying to retrieve session id for the in-person signing ceremony using Iframe.

Hello; I am trying to set up REST API integration for one of my clients. I've gotten as far as: 1) Create The Package 2) Add a Document 3) Create a Signer (Role) 4) Add the Signer I am now trying to send the document to the Signer. How does one do this? The Rest API that I have seen seems to make no mention of sending a document. TIA Ken Moorhead

Hi Is there a way to hide the Exit Document button? Can it be done at the account level? When I am creating a package, I am setting the HandOver (href, title, text ) object . Will the hiding it at the account level , override this package level setting. Regards Mario

We are trying to add multiple documents with Meta Data to the REST API in a single call. We are able to add a single document with meta data using a call like

POST /api/packages/CexKAcIADCrhmET2TheZdEtnnQA=/documents/ HTTP/1.1
Host: sandbox.esignlive.com
Authorization: Basic XXXXXXXXXXXXXXXXXXXXX
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW
Cache-Control: no-cache

------WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="payload"

 {
    "description": "A test document 1.",
    "name": "45-Sold Notice.pdf"
  }
------WebKitFormBou

Hi Does eSignLive have a healthcheck endpoint Regards mario

Hi, We have an onsite installation of esignlive and ewitness esl api shows following version at /api/sysinfo { "schema": "16.10.4", "version": "16.6.16", "timestamp": "2017-12-12 23:32+0000" } I'm attempting to extract the full evidence pdf and html via both the e‐Witness™ UI "Export the Archive in PDF" and the "Export the Archive in HTML" function as well as via the /evidence/api/v2/{guid}/{format}/{compress} rest endpoint call While the e‐Witness™ UI displays the evidence, both the UI "Export the Archive in PDF" and the "Export the Archive in HTML" and rest endpoin