Electronic signature API.

An electronic signature API is a set of REST endpoints that let your own application send documents for signature, collect legally binding signatures, and track their status, all in code and without anyone logging into a signing product. Instead of a person uploading a PDF and clicking Send, your backend calls an endpoint like POST /v1/documents, adds the signers, and the API handles delivery, reminders, signing, sealing, and the audit trail. You get the signed PDF and a certificate of completion back through a webhook. It is how software products embed signing directly into their own onboarding, contract, or checkout flows.

Request a free sandbox account. The Document eSign API is rolling out to customers now, and access is granted per account rather than through open self-serve signup at this stage. We provision a workspace, issue you a test and a live API key, and share the full endpoint reference so your team can start integrating against the sandbox the same day. There is no charge to build and test in the sandbox, and you only pay once you send live envelopes.

Yes. You can generate a signing URL for any recipient and either redirect the signer to it or drop it into an iframe inside your own app, so the person never leaves your product to sign. The signing page can be fully white-labeled to your brand and hosted on your own domain, which means no third-party logo, no Powered by footer, and a signing experience that looks like a native part of your software rather than a bolt-on.

Yes, through webhooks. You register an endpoint on your server and the API sends a signed event payload every time something meaningful happens, such as a recipient viewing a document, a recipient signing, a document completing, or a signer declining. Each webhook is signed so you can verify it came from us, and delivery retries on failure. This is what lets you update your own database, advance a workflow, or trigger the next step the moment a contract is signed, without polling for status.

The API is $0.40 USD per envelope, where an envelope is one document package sent for signature regardless of how many signers or pages it contains. Plans start at $20 a month with 40 envelopes included, there is no per-seat license, and building and testing against the sandbox is free. High-volume and white-label deployments get custom volume pricing. Talk to sales for a rate scoped to your expected monthly volume.

Yes. Signatures collected through the API carry the same legal standing as ones collected in the web app, and are binding under the U.S. ESIGN Act and state UETA laws and under the EU eIDAS regulation. Every completed document is sealed with a SHA-256 hash and a PAdES-B-LT signature carrying an independent timestamp, and ships with a certificate of completion that records each signer's email, IP address, and timestamp on an append-only audit log. That is the same verifiable evidence trail the product produces everywhere else, available to you programmatically.

Yes. Approved accounts get the full REST reference covering documents, recipients, fields, templates, and webhooks, with copy-paste examples for each endpoint. The API speaks plain JSON over HTTPS, so it works from any language or framework with an HTTP client, and you can call it directly with curl while you prototype. Language SDKs and a Postman collection are part of the rollout. Request access to get the current reference and your sandbox keys.