eSora Sign API

Send your first document for signature with one API call.

API keys, what they can do, and how to keep them safe.

Every error has an HTTP status, a stable code and a message you can show.

Lists are newest first and use cursors.

Retry safely: the same request with the same key never happens twice.

How fast you can call the API.

The API version and how changes are made.

Signed notifications to your server when documents change.

Let people sign inside your own website or app.

Make a document once, then send it to new people with one call.

Connect AI assistants to eSora Sign with the MCP connector.

A document is one or more PDFs sent to people to sign or to receive a copy. It goes from draft to sent to completed, or ends as declined, voided or expired.

The people on a document: signers, and people who get a copy (cc).

Where each signer signs, initials, dates or fills in. Positions are fractions of the page.

Automatic reminder emails to signers who haven’t signed yet.

Reusable documents with roles. Make them in the app, then send them with the API.

Your workspace’s address book. People you send to are added automatically.

Group documents in folders, shared across the workspace.

Where we send signed event notifications. See the Webhooks guide.

What happened to your documents in the last 90 days. The same events webhooks deliver.

Who the key acts as, and the workspace it belongs to.

Keys for the API and the MCP connector. The secret is shown once.

Check whether a PDF is an unchanged document signed with eSora Sign. No API key needed.