REST API

When I signed the document I see 2 popups (I open document in iframe using signing url) First one for confirm "Please click OK to confirm your signatures to this document or click Cancel to review it again before submission"esinglive_1.PNG and second one for completion and redirect"esinglive_2.png" What I want to do is when I click on first modal(confirm) it will redirect where I want without showing second one using nodejs

Hi there, I just start to use this function in our platform, and when I try to fetch all packages' info, I notice the response only contains 1 package details even the "count" value is 2. Could you pls help to check? Thanks a lot in advance. Code segment: http.url = 'https://sandbox.e-signlive.ca/api/packages'; http.followRedirects = true; http.httpMethod = 'get'; ..... var response = http.retrieveWithoutException(); var pluto = response.getBodyAsText(); ret = 'Code:' + response.getStatusCode(); ret += '
pkgID:' + JSON.parse(pluto) ['id']; return ret. Result: pls refer the attachment

Hi, I want to upload document on package, document uploading working fine. I also want to add roles and approvals through code.

I am following the example in your blog to Authenticate a Signer: https://www.esignlive.com/blog/esignlive-how-to-authenticating-signers/ Here is what I have produced: var apiKey = CeremonyClient.GetKey(); var urlBase = CeremonyClient.GetUrl(); // "https://sandbox.e-signlive.com/api" var json = authList.Aggregate("{\"auth\":{\"challenges\":[", (current, t) => current + ("{\"question\":" + t.Question + ",\"answer\":" + t.Answer + "},")); json += "],\"scheme\":\"CHALLENGE\"}"; var jsonContent = new StringContent(json, Encoding.UT

Hello, when i execute the following REST API call (https://sandbox.esignlive.com/api/packages) the results includes the current total transaction count, with only the most recently package / transaction json data. is this the expected behavior?

Hi, I want to get pdf document. In POSTMAN var request = require("request"); var options = { method: 'GET', url: 'https://sandbox.esignlive.com/api/packages/{packageId}/documents/{documentId}/pdf', headers: { 'postman-token': '731de084-90fd-c0ac-2fff-346723de7315', 'cache-control': 'no-cache', 'content-type': 'application/json', accept: 'application/pdf', authorization: 'Basic -----------------------------------------------------------==' } }; request(options, function (error, response, body) { if (error) throw new Error(error); console.log(body); }); But I

This one is actually both a question and its answer. I just received a question from an integrator who is trying to define a date field. Other topics probably cover this but I thought I would take a minute to create one dedicated specifically to this topic. Bound fields are a little tricky. A date field looks like this:

{
   "top": 319.8,
   "left": 373.1,
   "width": 261.3,
   "height": 98.8,
   "page": 0,
   "type": "INPUT",
   "subtype": "LABEL",
   "value": "MMMM dd, yyyy",
   "binding": "{approval.signed}"
}

Bound fields are actually "INPUT" fields of subtype "LABEL".

Hello gurus. I hope you can help me. I'm trying to create a new package in sandbox.esignlive.com, but when I try to upload the document I'm getting: HTTP/1.1 415 Unsupported Media Type Basically I'm trying to reproduce the same calls as you are making in your PHP example, so: 1) I'm creating a package, lets say ID: s0ex3xuyXSxaUT16bzcYcwRr660= 2) Next I'm trying to POST to https://sandbox.esignlive.com/a/api/packages/s0ex3xuyXSxaUT16bzcYcwRr660= where my post is a multipart/form-data containing a pdf and the entire xml including the approvals, and the custom fields. First part is OK, and I'm

Hey! I've used this codebase to put up a quick testing app: https://www.esignlive.com/blog/esignlive-how-to-creating-a-simple-php-web-application/ Unfortunately I am stuck for a day or so with a 400 error at this point:

POST /api/packages/A8e11I57ytWC1GHJzzphfLISw04=/documents/signed_documents HTTP/1.1
Host: sandbox.esignlive.com
Accept: */*
Authorization: Basic api_key
Content-Type: application/json
Content-Length: 138

The package is created successfully in the sandbox account, the signer is added as well but it cannot be set to SENT, as it yields a Bad Request error.

Hello, I have scenario in which I am sending packages to two users in order through signing URL. I have tested, it is working fine. 1) user 1 signs document (working) 2) user 2 approve/disapprove (working) Now what I want to do : 1) user 2 able to edit the document 2) Edited document can be sent back to user 1 . I am using REST API Can any one help me out, or let me know how to do it.