Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Preferences
Replies
Topics Started
Topic Started
Topics |
---|
Hello,
In the attached image, a signature properties interface we can see the Location: Client IP 172.16.4.81
|
Hello I created a package but removed the Electronic Disclosures and Signatures Consent.
So I have a package with just one document.
|
I am making the following call
https://sandbox.esignlive.com/api/packages/uUoiB-Htq5GXIvRN9VeDcjrMXYE=/documents/default-consent/approvals/b838ff5f-d63e-4a63-af92-fb2ec7fe9b98/signand send |
Hello, I am getting the following response, and I believe that I am sending the correct data.
I will copy here the request I am making
request: { debugId: 1, uri: 'https://sandbox.esig |
Replies Created
Reply to: This signature is not assigned to you for signing. response
Thursday, July 5, 2018 at 04:55amI have done that and removed the apikey from the request, but now I am getting unathorized session,
body: { messageKey: 'error.unauthorised.noSession', message: 'Failed to retrieve Session', code: 401, name: 'Unauthorized' }
Reply to: This signature is not assigned to you for signing. response
Thursday, July 5, 2018 at 05:35amWell probably not. How can I get the ESIGNLIVE_SESSION_ID?
Reply to: This signature is not assigned to you for signing. response
Friday, July 6, 2018 at 12:34amOk this working now.
So I just need your help regarding two more calls.
One is the call for the signer to confirm the consent-document.
And the other call is the call to confirm the signature. So after I make this call
https://sandbox.esignlive.com/api/packages/soem_package_id/documents/some_document_id/approvals/some_approval_id/signI need to make another one to confirm the signature. Could you please tell me what that call is, and what type of payload I need to send?
Reply to: This signature is not assigned to you for signing. response
Monday, July 9, 2018 at 11:42pmHello, I am doing the request to bulk sign but getting This signature is not assigned to you for signing.
This is my request
{ request: { debugId: 3, uri: 'https://sandbox.esignlive.com/api/packages/i2ULoALa37cb4jimHnHsvcnrNqs=/documents/signed_documents', method: 'POST', headers: { Cookie: 'ESIGNLIVE_SESSION_ID=xxxxxxxx', host: 'sandbox.esignlive.com', accept: 'application/json', 'content-type': 'application/json', 'content-length': 98 }, body: '{"documents":[{"id":"default-consent"},{"id":"b6960c2641cd63503866cef5ce364a9772ff61436ceae70d"}]}' } }And this is the reply:
body: { messageKey: 'error.forbidden.signatureNotAssigned', message: 'This signature is not assigned to you for signing.', code: 403, name: 'Access Denied' }
Reply to: Package without Electronic Disclosures and Signatures Consent issue
Tuesday, July 31, 2018 at 04:21amMaybe, I did not make myself clear. I know I only wish to sign a document, and I thought I could use Bulk Sign API call to sign that document.
The problem is that I am not able to sign the document with the Bulk Sign API call. Could this have anything to do with the fact that I removed the Electronic Disclosures and Signatures Consent?
Subscriptions
Topics | Replies | Freshness | Views | Users |
---|---|---|---|---|
Hello,
In the attached image, a signature properties interface we can see the Location: Client IP 172.16.4.81
|
5 | 2 years 9 months ago | 51 | |
Hello I created a package but removed the Electronic Disclosures and Signatures Consent.
So I have a package with just one document.
|
3 | 5 years 9 months ago | 23 | |
I am making the following call
https://sandbox.esignlive.com/api/packages/uUoiB-Htq5GXIvRN9VeDcjrMXYE=/documents/default-consent/approvals/b838ff5f-d63e-4a63-af92-fb2ec7fe9b98/signand send |
1 | 2 years 8 months ago | 13 | |
Hello, I am getting the following response, and I believe that I am sending the correct data.
I will copy here the request I am making
request: { debugId: 1, uri: 'https://sandbox.esig |
15 | 5 years 4 months ago | 83 |
Subscriptions Release Notes
This user is not subscribed to any release notes.