Is there anyway to suppress the automatic email to signers on package creation? We would like to give our application user the option to sign now (we will retrieve signing URLs), or sign by email (appears to be sent automatically at package creation). The REST API request for creating the package in eSignLive is throwing "error.validation.userAddition.invalidEmail" when removing the email from json payload.
I have seen many posts and guides on how to create a Signer Workflow which enables signing in sequence or succession. We have a requirement to allow our signers to sign at their own convenience in any order they choose. Can this be accommodated as well? If so, could someone please share the REST API code that would accomplish this so I may compare to our current json payload which has the signers indexed and is requiring succession signing ceremony. I have attached a snippet of code from the feature guide on Signer Workflow.
Hello, Am receiving the below error on deleting a document. When does this error occur? "Exception":"Silanis.ESL.SDK.EslServerException: Could not delete document from package. Exception: The remote server returned an error: (400) Bad Request. HTTP DELETE on URI https://sandbox.esignlive.com/api/packages/Vk-Wf0lNYV0PSC-7DN4lD1dZ3W4=/documents/consent-Buyer.
Hi I am looking for an API which would help me generate a eSL report. Currently 'eslClient.reportService.downloadDelegationReportAsCSV(dateStart, dateStop)' provides with most of the information that I am looking for but I need some more details(columns) for a PACKAGE as follows: UpdatedDate EndDate NumberOfDays Document Count ListOfSigners Is it possible to get this information from ReportService? Thank you for your help!
What happens when the server that is setup to receive callbacks isn't available due to a network issue or an issue with the server itself. Are any attempts made to retry the notification. Also, are there any suggestions on how to handle the integration situation if it isn't possible to receive callbacks due to firewall rules? Should the integrator create some sort of polling to check the status of open packages and their signers that it has sent or is there a better solution? Thanks, Jimmy