canonical: https://jentic.com/apis/eversign.com/eversign-e-signature-api

# Eversign Xodo Sign (Eversign) E-Signature API

Jentic publishes the only available OpenAPI specification for Xodo Sign (Eversign) E-Signature API, keeping it validated and agent-ready. Xodo Sign (formerly eversign) is a legally-binding electronic signature platform that lets agents and applications create signature documents, dispatch them to multiple signers, manage reusable templates, and run bulk-send signing jobs. The API surfaces 17 endpoints covering document lifecycle, template management, business switching for multi-tenant accounts, and signer reassignment. Documents are tracked from draft through completion with reminders, cancellation, trash, and final PDF download supported in a single workflow.

## For AI agents

Send documents for signature, manage templates, and orchestrate bulk-signing flows on Xodo Sign (formerly eversign), with full lifecycle tracking from creation to signed PDF.

## Scope

Does not handle document drafting, contract clause libraries, or payment collection - use for electronic signature workflows on prebuilt documents only.

## Capabilities

- Create signature documents and dispatch them to one or more signers via /document
- Manage reusable signing templates so agents can fire off recurring NDAs or contracts in one call
- Send signer reminders and reassign signers without re-creating the document
- Cancel in-flight documents and move completed ones to trash through dedicated endpoints
- Switch between multiple Xodo Sign businesses on a single account using /business
- List documents filtered by status (drafts, completed, templates, archived) for downstream automation

## Use cases

### Contract E-Signature Workflow

Send sales contracts, NDAs, and offer letters out for signature without leaving the agent runtime. The Xodo Sign API accepts a document payload with signers and fields, returns a signing URL for each party, and exposes status polling and reminder endpoints for chasing slow signers. Most contracts are fully signed and downloadable as PDFs within minutes once recipients open the email.

Example prompt: Create a signature document for an employment offer, add two signers (employer, candidate), send it, then poll until status is completed and download the final PDF

### Template-Driven Bulk Signing

Operations teams routinely send the same vendor NDA, employee handbook, or onboarding form to dozens of recipients. Saving the document as a Xodo Sign template once and then re-using it via the document endpoint lets an agent fire off a personalised signature request in a single call, cutting per-recipient send time from minutes to under a second.

Example prompt: List existing templates via GET /document?type=templates, pick the vendor NDA template, then create a new document from it for vendor@example.com

### Document Lifecycle Management

Compliance teams need a clean audit trail showing which contracts are pending, signed, cancelled, or trashed. The Xodo Sign API exposes filtered list endpoints by document type plus dedicated cancel and trash endpoints, so an agent can produce a weekly status report or auto-cancel stale documents older than 30 days.

Example prompt: List all documents with type=all, filter to those pending for more than 30 days, and call /document_cancel for each

### AI Agent E-Signature Integration via Jentic

An AI agent embedded in a sales CRM can take a generated contract, send it to the prospect through Xodo Sign, and report status back to the rep without the rep ever opening a signature tool. Jentic exposes the Xodo Sign document endpoints as MCP tools so agents can search 'send a contract for signature', load the input schema, and execute in one flow.

Example prompt: Use Jentic search 'send a document for electronic signature' to find the Xodo Sign create-document operation, load the schema, and execute with a pre-filled NDA payload

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/document` | Create a new signature document |
| GET | `/document?type=all` | List documents filtered by status |
| GET | `/document?type=templates` | List saved templates |
| POST | `/send_reminder` | Send a reminder to a pending signer |
| POST | `/reassign_signer` | Reassign a signer on a pending document |
| POST | `/document_cancel` | Cancel a pending document |
| POST | `/document_trash` | Move a document to trash |
| GET | `/business` | List businesses on the account |

## Key resources

- **document** — Create, list, cancel, trash, and download signature documents
- **template** — Reusable document templates for high-volume sending
- **business** — Switch active business when an account spans multiple companies
- **send_reminder** — Nudge signers who have not yet completed a document
- **reassign_signer** — Replace a signer on a pending document without restarting the workflow

## Why Jentic

- **Setup:** Wiring the Xodo Sign (Eversign) E-Signature API by hand means passing your API key as the access_key query parameter, pointing at the api.eversign.com host, and coding the document create, reminder, and cancel calls yourself. Through Jentic you install once, import the Xodo Sign E-Signature API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This Xodo Sign API identifies documents through request payloads rather than URL path ids, so scope the agent to the operations it needs, such as creating a document and sending a reminder, rather than to one document. You choose the operations it may call, so destructive ones like cancelling or trashing a document are not included unless you add them.
- **Credential handling:** Your Xodo Sign API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a document for electronic signature' or 'send a signing reminder', and Jentic returns the matching Xodo Sign operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Xodo Sign (eversign) API** — A leaner Xodo Sign spec covering 9 endpoints with hash-based document paths.
- **Dropbox Sign API** — Dropbox Sign (formerly HelloSign) covers the same e-signature workflows with stronger SDK support.
- **PandaDoc API** — PandaDoc adds CPQ, proposal templates, and payment collection on top of e-signature.

## FAQ

### Why is there no official OpenAPI spec for Xodo Sign (Eversign) E-Signature API?

Xodo Sign does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Xodo Sign (Eversign) E-Signature API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Xodo Sign (Eversign) E-Signature API use?

The API uses an API key passed as an apiKey credential against the api.eversign.com base URL. Through Jentic, the key is stored encrypted in your Jentic One instance and never enters agent context - agents receive scoped execution rights, not the raw key.

### Can I send the same NDA to many signers with the Xodo Sign (Eversign) E-Signature API?

Yes. Save the NDA once as a template via the document endpoint with type=templates, then create a new document from that template for each recipient. List templates with GET /document?type=templates and reference the template hash in subsequent POST /document calls.

### What are the rate limits for the Xodo Sign (Eversign) E-Signature API?

The OpenAPI spec does not declare quantitative rate limits; Xodo Sign throttles based on plan tier. Inspect 429 responses and the Retry-After header in production, and contact Xodo Sign support to confirm your account's limits before high-volume bulk sending.

### How do I send a document for signature through Jentic?

Run pip install jentic, then use the async pattern: await client.search('send a document for electronic signature'), await client.load(...), await client.execute(...). The search returns the POST /document operation with its input schema so the agent can pass a signers array and document fields directly.

### Can I cancel a Xodo Sign signature document after sending it?

Yes. Call POST /document_cancel with the document hash. Cancelled documents stop sending reminders and cannot be signed; use /document_trash afterwards if you also want them removed from the active list.

### Can I limit what my agent is allowed to do with the Xodo Sign E-Signature API?

Yes. Because you run Jentic One yourself, your own rules decide which Xodo Sign operations and credentials the agent may use. This API identifies documents through request payloads rather than URL path IDs, so you scope by operation: grant only the calls the agent needs, such as creating a document with POST /document or nudging a signer with POST /send_reminder. Destructive operations like POST /document_cancel and POST /document_trash stay off-limits unless you explicitly add them.