Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Approved Answers
Replies
Topics Started
Preferences
Topic Started
Topics |
---|
Team,
I am looking for help with below scenarios
1) To add a signer to a transaction, is signer emaild id mandatory in signer json request?
2) What if we have a scenario, where a couple wants
|
At my work place, we are trying to get a Sender Authentication token for a package using the below information
/api/authenticationTokens/sender
Authorization and Accept Headers are included.
In Bo
|
When I do PUT request to /api/packages/{package_id} with request payload as
{
"status": "DRAFT"
}
I get error response as
{
"code": 415,
"entity": null,
"message": "Unsupported Media
|
Apart from the feature guides, where can I find the complete documentation for all the REST API features available?
In some cases, I found different examples, and the URI was different.
|
We have a requirement, to setup a group of signers, where the email notification goes to a email group, and whoever part of that group can pick the request from queue and make progress in signing cere
|
Replies Created
Reply to: PDF with multiple Signature Capture Fields - some of which are optional
Tuesday, August 29, 2017 at 04:46pmIts a great article and real time need every business goes through. Was any enhancement made around this option fields?
Any documentation around Text extraction fields?
For our case, I can't define the Role id in Roles object related to specific field id or so, is it possible to put some hidden text on PDF wherever we needed and then link that text to Signer name/Initials/click to sign type when creating the package?
Similar to this example, we also have a requirement, where the number of Signers does change for each transaction, but on document we have fields defined to accommodate maximum possible signers.
I know the possible signers for a given transaction and all the pre-defined fields(which will have hidden text), is their any way, I can define to link the fields to signer at run time, so that I dont have to do any clean up or so in post creation process before updating package status to SENT?
Reply to: In-person session in an iframe
Wednesday, September 13, 2017 at 07:28amHey Mike,
In this article, the resource URI for Token API is different than the article I am referring to.
I am referring to is, http://docs.esignlive.com/content/c_integrator_s_guide/rest_api/authentication_tokens.htm
Can you please confirm, what is the latest API we need to go through?
Is their API page for eSign, where it lists every available feature with documentation other than the Feature Guides?
Thanks for your help.
Reply to: Document upload to package using REST API failing
Monday, August 7, 2017 at 06:09pm
Trying to upload document to Transaction using REST API, getting error.
Please refer to attachment for req and resp error.
I tried following the article or instructions following provided in the Document upload using Postman article.
Reply to: Document upload to package using REST API failing
Monday, August 7, 2017 at 06:15pm
Req---
--------------------------------------------------------------------------------------------------------
POST https://sandbox.esignlive.com/api/packages/ggj1mkdQEWLsmP1tsWSj7T9sbjQ=/documents HTTP/1.1
Host: sandbox.esignlive.com
Connection: keep-alive
Content-Length: 186008
Accept: text/html
Cache-Control: no-cache
Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop
Authorization: Basic XXXXXXXXXXXXXX
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
Postman-Token: ae3a1c88-221a-fbd2-a051-f109fe80e5be
Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryKwCjv7NIJBI7cAxg
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.8
------WebKitFormBoundaryKwCjv7NIJBI7cAxg
Content-Disposition: form-data; name="file"; filename="cleaning_contract.pdf"
Content-Type: application/pdf
ALL THE FILE PDF CONTENT is replaced.
------WebKitFormBoundaryKwCjv7NIJBI7cAxg--
--------------------------------------------------------------------------------------------------------
Response ---
HTTP/1.1 302 Found
Server: nginx
Date: Tue, 08 Aug 2017 03:04:25 GMT
Content-Length: 0
Connection: keep-alive
X-Powered-By: Undertow
Location: https://sandbox.esignlive.com/error?error=eyJtZXNzYWdlS2V5IjoiZXJyb3IuaW50ZXJuYWwuZGVmYXVsdCIsIm1lc3NhZ2UiOiJVbmV4cGVjdGVkIGVycm9yLiBXZSBhcG9sb2dpemUgZm9yIGFueSBpbmNvbnZlbmllbmNlIHRoaXMgbWF5IGhhdmUgY2F1c2VkIHlvdSwgcGxlYXNlIHRyeSBhZ2Fpbi4gSWYgdGhlIHByb2JsZW0gcGVyc2lzdHMsIHBsZWFzZSBjb250YWN0IG91ciBzdXBwb3J0IHRlYW0uIiwiY29kZSI6NTAwLCJuYW1lIjoiVW5oYW5kbGVkIFNlcnZlciBFcnJvciJ9
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Strict-Transport-Security: max-age=31536000; includeSubdomains;
--------------------------------------------------------------------------------------------------------
Reply to: Document upload to package using REST API failing
Tuesday, August 8, 2017 at 05:57amHey Haris,
Sorry, because of binary or so, I had issues with the post, and had to update multiple times. Initially, the Post was not even showing up and was empty after sometime, so I have to do multiple updates.
But this morning, I see all together. I wanted to make sure my request is valid, so posted the maximum information I can.
Yes, I am following your example article as is with many trials, however, here is the latest simple test I did with no luck and as per your request, I have attached the screenshot of Postman.
Please let me know if you need any additional information.
Subscriptions
Topics | Replies | Freshness | Views | Users |
---|---|---|---|---|
Team,
I am looking for help with below scenarios
1) To add a signer to a transaction, is signer emaild id mandatory in signer json request?
2) What if we have a scenario, where a couple wants
|
1 | 6 years 4 months ago | 15 | |
At my work place, we are trying to get a Sender Authentication token for a package using the below information
/api/authenticationTokens/sender
Authorization and Accept Headers are included.
In Bo
|
7 | 6 years 6 months ago | 100 | |
Hi, does the URL given by https://sandbox.esignlive.com/api/packages/{id}/roles/{id}/signingUrl expire? If so, is it configurable?
Thanks, Jimmy
|
1 | 6 years 7 months ago | 73 | |
Hi Team,
We are using rest API to communicate with esign live .
|
1 | 6 years 7 months ago | 19 | |
When I do PUT request to /api/packages/{package_id} with request payload as
{
"status": "DRAFT"
}
I get error response as
{
"code": 415,
"entity": null,
"message": "Unsupported Media
|
7 | 6 years 7 months ago | 108 |
Subscriptions Release Notes
This user is not subscribed to any release notes.