Xodo Sign (Eversign) E-Signature API

Name: Xodo Sign (Eversign) E-Signature API API
Brand: Xodo Sign (Eversign) E-Signature API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationapiKey17 EndpointsREST

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

Connect the Xodo Sign (Eversign) E-Signature API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Xodo Sign (Eversign) E-Signature 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) E-Signature API API.

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

GET STARTED

Start building with Xodo Sign (Eversign) E-Signature API API

Explore with Jentic

View OpenAPI Document

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

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.

Use Cases

Patterns agents use Xodo Sign (Eversign) E-Signature API API for, with concrete tasks.

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

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.

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.

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.

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

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

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

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

Why though Jentic?

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

Credential isolation

The Xodo Sign API key is stored encrypted in the Jentic MAXsystem vault. Agents receive scoped execution rights — the raw apiKey is injected at call time and never appears in agent context, prompts, or logs.

Intent-based discovery

Agents search by intent (e.g. 'send a document for electronic signature') and Jentic returns the matching Xodo Sign POST /document operation with its complete input schema, so the agent can fill signer details without reading vendor docs.

Time to first call

Direct Xodo Sign integration: 1-2 days for auth, signer payload construction, and webhook polling. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Xodo Sign (eversign) API

A leaner Xodo Sign spec covering 9 endpoints with hash-based document paths.

Choose this when working with the /api base URL and path-style document IDs (/document/{hash}) instead of the legacy query-style endpoints.

Alternative

Dropbox Sign API

Dropbox Sign (formerly HelloSign) covers the same e-signature workflows with stronger SDK support.

Choose Dropbox Sign when the team already runs on Dropbox or needs deeper signing-room and team-management features.

Alternative

PandaDoc API

PandaDoc adds CPQ, proposal templates, and payment collection on top of e-signature.

Choose PandaDoc when the agent needs to combine document generation, pricing tables, and signatures in one platform.

FAQs

Specific to using Xodo Sign (Eversign) E-Signature API API through Jentic.

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

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