canonical: https://jentic.com/apis/eversign.com/eversign-xodo-sign

# Eversign Xodo Sign (eversign) API

Jentic publishes the only available OpenAPI specification for Xodo Sign (eversign) API, keeping it validated and agent-ready. Xodo Sign is a RESTful JSON API for e-signature workflows that uses path-style document hashes (e.g. `/document/{document_hash}`) and groups operations under the /api base URL. The 9-endpoint surface covers document creation, retrieval by hash, cancellation, signed-PDF download, signer reminders, and template listing. It is best suited for agents that need clean hash-based document IDs rather than the legacy query-string variant.

## For AI agents

Send and track signature documents through Xodo Sign using clean hash-addressed endpoints, including cancel, reminder, and final-PDF download.

## Scope

Does not handle document drafting, contract clause libraries, or in-document payments - use for sending and tracking e-signature requests only.

## Capabilities

- Create signature documents with multiple signers via POST /document
- Retrieve a single document's full state by hash with GET `/document/{document_hash}`
- Cancel a pending document via POST `/document/{document_hash}/cancel`
- Download the final signed PDF once all parties complete signing
- Send reminders to outstanding signers on a specific document
- List reusable templates from the /template endpoint for repeat sending

## Use cases

### Hash-Addressed Document Workflow

Operations teams that prefer clean RESTful URL paths use this Xodo Sign variant because every document is addressed by a hash in the path rather than a query string. Agents create a document, capture the returned hash, and then GET, cancel, or remind on `/document/{document_hash}`/* without needing to manage extra query parameters.

Example prompt: POST /document to create a signature document, capture the returned document_hash, then GET `/document/{document_hash}` every 60 seconds until status is completed

### Signer Reminder Automation

Sales and HR agents often need to chase signers who have not yet signed offer letters or contracts. The `/document/{document_hash}/send_reminder` endpoint nudges all outstanding signers in one call, letting an agent run a daily sweep that reminds anyone whose document has been pending more than 48 hours.

Example prompt: List documents pending more than 48 hours, then POST `/document/{document_hash}/send_reminder` for each one

### Signed PDF Retrieval for Records

Compliance pipelines need to archive every signed contract into long-term storage as soon as the last signature lands. The download_final_pdf endpoint returns the fully signed PDF for any completed document, so an agent can fetch and ship it to S3, Drive, or a DMS within seconds of completion.

Example prompt: On document-completed event, GET `/document/{document_hash}/download_final_pdf` and upload the binary response to compliance archive

### AI Agent Signing Tool via Jentic

An AI sales assistant uses Jentic to discover the Xodo Sign create-document operation and execute it from a CRM workflow. The agent never touches vendor docs - it searches by intent, gets the input schema, and sends contracts to prospects directly inside the conversation thread.

Example prompt: Use Jentic search 'send a document for signature' to find Xodo Sign POST /document, load schema, and execute with prospect contact details

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/document` | Create a signature document |
| GET | `/document/{document_hash}` | Retrieve a document by hash |
| POST | `/document/{document_hash}/cancel` | Cancel a pending document |
| POST | `/document/{document_hash}/send_reminder` | Send signer reminders |
| GET | `/document/{document_hash}/download_final_pdf` | Download the signed PDF |
| GET | `/template` | List templates |
| GET | `/business` | List businesses |

## Key resources

- **document** — Create, fetch, cancel, and download signature documents by hash
- **template** — List reusable signing templates
- **business** — List businesses on the Xodo Sign account
- **send_reminder** — Trigger reminder emails to outstanding signers

## Why Jentic

- **Setup:** Wiring the Xodo Sign (eversign) API by hand means passing your API key as the access_key query parameter, tracking the api.eversign.com/api base path, and coding the document create, reminder, and download calls yourself. Through Jentic you install once, import the Xodo Sign API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Xodo Sign puts the document hash in the URL path (`/document/{document_hash}`), so a rule can pin your agent to one document for reading, reminders, and final-PDF download. You choose the operations it may call, so cancelling a document is not included unless you add it.
- **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 signature' or 'download the final signed PDF', 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) E-Signature API** — Wider 17-endpoint Xodo Sign surface with bulk-send and signer reassignment.
- **Dropbox Sign API** — Dropbox Sign (HelloSign) for e-signature with deeper SDK and team-management support.
- **BoldSign API** — BoldSign offers e-signature with built-in audit trails and lower per-document pricing.

## FAQ

### Why is there no official OpenAPI spec for Xodo Sign (eversign) 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) 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) API use?

The API uses an apiKey credential sent against api.eversign.com/api. Through Jentic, the key lives in your Jentic One instance and is injected at execution time so the agent never sees the raw secret.

### How do I cancel a pending Xodo Sign document?

Call POST `/document/{document_hash}/cancel` with the document hash returned when you created the document. The document immediately stops accepting signatures and signers see a cancellation notice on next access.

### What are the rate limits for the Xodo Sign (eversign) API?

The spec does not declare specific rate limits; Xodo Sign throttles based on plan. Watch for 429 responses and the Retry-After header, and confirm your account ceiling with Xodo Sign support before high-volume runs.

### How do I download a signed PDF through Jentic?

Run pip install jentic, then await client.search('download a signed e-signature pdf'), client.load, and client.execute. Jentic surfaces GET `/document/{document_hash}/download_final_pdf` with the document_hash parameter wired into the input schema.

### Can I send signer reminders without re-creating the document?

Yes. POST `/document/{document_hash}/send_reminder` triggers reminder emails to every signer who has not yet signed; the document state is unchanged.

### Can I limit what my agent is allowed to do with the Xodo Sign (eversign) API?

Yes. Because you run Jentic One yourself, your own rules decide which Xodo Sign operations your agent may call and which credential it uses. Since the document hash lives in the URL path (`/document/{document_hash}`), you can pin the agent to a single document for reading its state, sending signer reminders, and downloading the final signed PDF. You choose the operations it may call, so an action like cancelling a document via POST `/document/{document_hash}/cancel` is excluded unless you explicitly allow it.