Account


Earned badges

Achievement: Latest Unlocked

Topic Started

Topics
We are having an intermittent issue with our REST API client.
We have set up our account with maximum allowed KBA failures = 3 but ESL is allowing seemingly unlimited invalid retries.
I read the following blog post: https://www.esignlive.com/blog/esignlive-setting-reminders And tried setting up reminders in my initial POST request that creates a signing package.
Our application submits signing packets via the REST API and receives callback notifications.
I need to set the package expiration date when I submit a package via the REST API with status=SENT. I have found the documentation on how to do this with the SDK but not with REST.

Replies Created

Reply to: Setting Up Reminders with REST

0 votes
Thank you, Duo. I'm trying to refactor my code according to this and now I'm running into another problem. The document that I attach to my initial POST to create the package in DRAFT status is not being saved. When I look at the resulting draft package in the ESL site, there is no document attached. And when I try to send a POST to change the status from DRAFT to SENT, it returns: {"code":400,"message":"Cannot send package without approvals.","messageKey":"error.validation.sendPackage.noApprovals","name":"Validation Error"} Up until now, I have been setting up everything, including the .pdf document and approvals, in the first POST request that creates the package. This works fine if status=SENT in the initial request. But now that I'm having to break this into three requests (create package, set up reminders, send package), this approach is no longer working. It looks like I'm going to have to create and attach my .pdf document in step 3 that sends the package. Is this right? Are there other things that I'm currently sending in my initial POST above that will have to be moved to the 3rd step, as well?

Reply to: Setting Up Reminders with REST

0 votes
Apparently something is wrong with my initial POST request. I switched it back to status=SENT and I get back the same response: {"code":400,"message":"Cannot send package without approvals.","messageKey":"error.validation.sendPackage.noApprovals","name":"Validation Error"} Here is my request. I don't see anything wrong with it. Do you? { "roles": [ { "locked": false, "emailMessage": { "content": "" }, "attachmentRequirements": [], "reassign": false, "specialTypes": [], "id": "BENJAMIN_J_KAPOSZTA", "data": null, "type": "SIGNER", "index": 0, "signers": [ { "auth": { "challenges": [ { "answer": "6789", "question": "What are the last 4 digits of your SSN or TaxID?", "maskInput": false } ], "scheme": "CHALLENGE" }, "company": "", "firstName": "BENJAMIN", "lastName": "KAPOSZTA", "phone": "", "email": "[email protected]", "knowledgeBasedAuthentication": null, "language": "en", "title": "", "external": null, "professionalIdentityFields": [], "userCustomFields": [], "delivery": { "email": true, "provider": false, "download": false }, "group": null, "signature": null, "address": null, "data": null, "name": "BENJAMIN J KAPOSZTA", "specialTypes": [], "id": "BENJAMIN_J_KAPOSZTA" } ], "name": "BENJAMIN J KAPOSZTA" } ], "documents": [ { "approvals": [ { "role": "BENJAMIN_J_KAPOSZTA", "signed": null, "accepted": null, "data": null, "fields": [ { "page": 0, "subtype": "FULLNAME", "width": 200, "binding": null, "extract": false, "extractAnchor": null, "left": 100, "top": 700, "validation": null, "height": 50, "data": null, "type": "SIGNATURE", "value": "" } ], "name": "Approval name" } ], "name": "Extension Agreement", "fields": [ { "name": "Next Due Date", "value": "9/28/2018" }, { "name": "Document Date", "value": "8/28/2018" }, { "name": "Borrower Name", "value": "BENJAMIN J KAPOSZTA" }, { "name": "Co-Signer Name", "value": "" }, { "name": "Account Number", "value": "514553056" }, { "name": "Effective Date", "value": "9/28/2018" }, { "name": "Months Extended", "value": "1" }, { "name": "Next Payment Due", "value": "9/28/2018" }, { "name": "New Maturity Date", "value": "8/28/2030" }, { "name": "Null Void Date", "value": "8/29/2018" } ] } ], "name": "Extension", "type": "PACKAGE", "language": "en", "emailMessage": "8/29/2018", "description": "Defines the terms of the Extension agreement", "autoComplete": true, "status": "SENT", "settings": { "ceremony": { "events": null, "inPerson": false, "declineButton": false, "declineReasons": [], "disableDeclineOther": false, "disableDownloadForUncompletedPackage": false, "disableFirstInPersonAffidavit": false, "disableInPersonAffidavit": false, "disableOptOutOther": false, "disableSecondInPersonAffidavit": false, "documentToolbarOptions": null, "handOver": null, "hideCaptureText": false, "hideLanguageDropdown": false, "hidePackageOwnerInPerson": false, "hideWatermark": false, "maxAuthFailsAllowed": 4, "optOutButton": false, "optOutReasons": [], "style": null, "layout": null } }, "due": "2018-08-29" }

Reply to: Setting Up Reminders with REST

0 votes
I discovered and fixed a bug I introduced earlier today while refactoring my code. I was sending a plain JSON string rather than a MultipartFormDataContent form. I fixed it and the package is being created successfully now using the three step process. It might take me a few days to confirm that the reminder emails are working. Thank you so much, Duo!

Reply to: KBA failure max tries not being enforced. Signers never get locked

0 votes
Thank you, Duo. I was misusing the term KBA. You are correct that I really meant QA. I will try setting maxAuthFailsAllowed in my API request and see if this resolves my issue. Is the KBA_Failure notification specific to KBA authentication? Or will it also be sent when the signer inputs an invalid QA answer?

Subscriptions

Topics Replies Freshness Views Users
We are having an intermittent issue with our REST API client.
3 5 years 1 month ago 56
Profile picture for user Duo_Liang
We have set up our account with maximum allowed KBA failures = 3 but ESL is allowing seemingly unlimited invalid retries.
6 5 years 7 months ago 81
Profile picture for user Duo_Liang
Profile picture for user roneddy
I read the following blog post: https://www.esignlive.com/blog/esignlive-setting-reminders And tried setting up reminders in my initial POST request that creates a signing package.
7 5 years 7 months ago 38
Profile picture for user Duo_Liang
Our application submits signing packets via the REST API and receives callback notifications.
1 5 years 8 months ago 28
Profile picture for user Duo_Liang
I need to set the package expiration date when I submit a package via the REST API with status=SENT. I have found the documentation on how to do this with the SDK but not with REST.
3 5 years 8 months ago 48
Profile picture for user Duo_Liang

Code Share

This user has not submitted any code shares.

Subscriptions Release Notes

This user is not subscribed to any release notes.