Question 1

What is an eSignature API?

Accepted Answer

An eSignature API is a set of REST endpoints that lets developers add electronic signature collection to any application. You send a document to the API with recipient details, the API handles delivery and signature capture, and returns a completed signed PDF with an audit trail via webhook.

Question 2

Is there a free eSignature API?

Accepted Answer

Yes. eSignature API includes a free plan with 50 legally binding documents per month, no watermark, and no credit card required. Unlike most competitors that offer sandbox-only test modes, eSignature API's free plan produces real production-quality signed documents from day one.

Question 3

How much does an eSignature API cost?

Accepted Answer

eSignature API uses credit-based pricing. Each completed signed document costs 10 credits, charged only on completion. Plans start free (50 credits/month) and scale from $29/month (1,200 credits) to $499/month (150,000 credits). PDF generation is included on all plans.

Question 4

What compliance standards does an eSignature API need to meet?

Accepted Answer

The key standards are: ESIGN Act and UETA for the United States, eIDAS (SES, AES, or QES) for the European Union, SOC 2 Type II for security certification, HIPAA for US healthcare applications, and GDPR for EU personal data. eSignature API meets ESIGN Act, UETA, eIDAS SES, SOC 2 Type II, and HIPAA standards on all plans.

Question 5

Is an eSignature legally binding?

Accepted Answer

Yes, in most jurisdictions. The ESIGN Act and UETA (US), eIDAS (EU), and equivalent laws in the UK, Australia, Singapore, and Canada give electronic signatures the same legal weight as handwritten signatures for most commercial agreements. Some exceptions apply for wills, certain real estate transactions, and notarised documents depending on jurisdiction.

Question 6

How do I add an eSignature to a PDF using an API?

Accepted Answer

You can generate a PDF from a template and collect the signature in one API call, or pass an existing PDF to the API for signing. Define recipient details and field positions in your request. The API handles delivery, collects signatures on any device, and returns the completed signed PDF with an audit trail via webhook.

Question 7

How do I build custom signing workflows with an eSignature API?

Accepted Answer

eSignature API supports sequential signing (signers complete in a defined order), parallel signing (all sign simultaneously), and five recipient roles: signer, approver, viewer, form filler, and carbon copy. Configure webhooks to trigger downstream actions on every signing event including sent, viewed, signed, completed, and declined.

eSignature API — Frequently Asked Questions