afrolkin

How to detect signature fields in package from PDF

0 votes
Hello, I'm trying to integrate eSign into my application using the REST API. I haven't been able to figure out how to create a package with signature field coordinates extracted from a PDF which already contains signature fields. Is there an available sample demonstrating how to ensure that the package detects the signature fields in the PDF (Rather than having to specify the coordinates of the signature field)? I've seen such samples for the SDKs, but have been unable to find one for the REST API. Thank you

Approved Answer

Reply to: How to detect signature fields in package from PDF

1 votes
Take a look at this example. You'll find a PDF and a C# class that makes a REST API call to create the package with the appropriate JSON to extract the fields from the PDF. Hope it helps. https://developer.esignlive.com/code-share/document-extraction-rest-api/

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: How to detect signature fields in package from PDF

0 votes
Using the same naming conventions for your fields as you'll see in this blog: https://www.esignlive.com/blog/e-signlive-how-to-document-extraction-net-sdk/ You should be able to simply set the "extract:" property in your package JSON payload (package level property) to true and the fields will be extracted. Let me know if you need a full example and I'll gladly get you one. :)

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: How to detect signature fields in package from PDF

0 votes
Thank you for the quick response. I've tried following the instructions in that guide before, and I wasn't able to extract the signatures. Following the guide, I've generated PDFs in acrobat with signature fields adhering to the nomenclature specified. After enabling the extract property and making the POST request I still haven't had any luck extracting the signatures yet. If you could provide a full sample with the REST API (preferably with a sample PDF as well), that would be great!

Reply to: How to detect signature fields in package from PDF

1 votes
Definitely. I will take a look at this in the morning and get you something, ASAP.

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: How to detect signature fields in package from PDF

0 votes
I tried with a JSON that looks something like the below with a field named [Signer1.Capture1] to extract signature field. The create package works but when I try retrieving the signing url it gives back an unexpected error. Not sure what is the issue. { "roles":[ { "id":"Signer1", "type":"SIGNER", "index":0, "signers":[ { "firstName":"Signer", "lastName":"1", "email":"[email protected]", "language":"en", "title":"" }], "name":"Signer1" }], "documents":[ { "approvals":[ { "role":"Signer1", "fields":[ { "id":"[Signer1.Capture1]", "page":0, "subtype":"CAPTURE", "extract":true, "type":"SIGNATURE" }], "name":"[Signer1.Capture1]" }], "name": "Test File" }], "name": "Test Package REST", "type":"PACKAGE", "language":"en", "description":"New Package", "autoComplete":true, "status":"SENT" }

Reply to: How to detect signature fields in package from PDF

1 votes
Thanks, that works perfectly!

Reply to: How to detect signature fields in package from PDF

1 votes
Awesome! Glad to help! :)

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off