Xodo Sign (eversign) API

Name: Xodo Sign (eversign) API API
Brand: Xodo Sign (eversign) API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationapiKey9 EndpointsREST

For Agents

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

Connect the Xodo Sign (eversign) API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Xodo Sign (eversign) API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Xodo Sign (eversign) API API.

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

GET STARTED

Start building with Xodo Sign (eversign) API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Xodo Sign (eversign) API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Xodo Sign (eversign) API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for xodo sign (eversign) api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Xodo Sign apiKey is stored encrypted in the Jentic MAXsystem vault. Agents receive scoped execution rights only — the secret is injected at call time and never enters prompt context.

Intent-based discovery

Agents call Jentic search with phrases like 'send a document for signature' and Jentic returns the matching POST /document operation along with the signer payload schema, removing the need to read vendor docs.

Time to first call

Direct Xodo Sign integration: about a day to wire auth and parse response payloads. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Xodo Sign (Eversign) E-Signature API

Wider 17-endpoint Xodo Sign surface with bulk-send and signer reassignment.

Choose this when you need bulk sending, signer reassignment, or document trash management beyond the 9-endpoint hash-style surface.

Alternative

Dropbox Sign API

Dropbox Sign (HelloSign) for e-signature with deeper SDK and team-management support.

Choose Dropbox Sign when the team is already on Dropbox or needs richer template editor and team controls.

Alternative

BoldSign API

BoldSign offers e-signature with built-in audit trails and lower per-document pricing.

Choose BoldSign when cost-per-document matters more than ecosystem fit.

FAQs

Specific to using Xodo Sign (eversign) API API through Jentic.

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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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.