Hi Team, I am trying create a package with pdf document part of package. I am getting below Error. {"messageKey":"error.validation.verifyDocument.couldNotBeFlattened","message":"Could not upload PDF document: it contains a syntax error preventing proper processing of its data.","code":400,"name":"Validation Error"} The PDF File i am using has PDF FORM Sigature Fields which were prepared by XML/SOAP based silanis Integration module. I have created Approval block with field to Extract existing Signature Blocks in PDF Form.
Hi Team, We have SOAP/XML based implementation in place, and want to move to the REST APIs. During the process,some module in our system would to prepare the Approval Blocks ( place holder for signatures) and same document is handover to other module which sends this file to Silanis for E-Signing process. I am trying to use the same document which has signature blocks ( set by other module). But Believe with REST API implementation, Signature Blocks need to be defined as part of JSON request payload ( Approvals- Fields.....
I want to request customer to upload his last tax return as part of a transaction. However, customer may actually has the tax return captured in many separate files (e.g. 1 page per file) as he is taking photos via his phone. I tried to upload 2 files against a single requested document and only the last uploaded file will be stored against the package. How can I allow uploading of many physical files against one single requested document?
Hi There, I am a newbie to eSignLive and is doing some research to see how we can improve our sales process. Our system currently generates contracts (PDF) dynamically and then email it to customer for signature. I know that through the eSignLive portal, I can mark up where in the PDF contract customer should sign. In order to automate the process, is there an API to upload the document as well as specify the location for signature? Is there any sample codes on how to do this?
I have been using a form field anchor [Signer1.Fullname1] to identify where a signature field is supposed to go when sent through the API. However, most of the documents we create in our system are done so using fpdf, so there will not be any form fields to name. Is there a simple text anchor that can be used to identify a signature field location? If not, what other options are there to let the system know where the signature field will go?
Can you please provide an overview of how QR code works? If a QR code is created for an eSign package, is there a time limit for how long the QR code will work? There is a client who wants to print the QR code and scan it with the app at a later date to avoid using a desktop computer. They tested it right away and it worked fine but who knows what will happen a few days out.
Hello Team, As per our understanding on sign any where feature the link of the document will be emailed to the email provided and pin details will be provided to mobile number.If the user doesn't have mobile number or they are not providing mobile number is their any possibility of providing pin to the user ??? Thanks, Navya.