Eversign Xodo Sign (Eversign) E-Signature API
Browse all Eversign APIs46
AI ReadinessFoundational (D)46/100
Agent-ready OpenAPI document · curated by JenticProductivityCollaborationapiKey17 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
Use for: I need to send a contract for electronic signature, I want to create a reusable NDA template in Xodo Sign, Send a reminder to a signer who has not completed the document, List all completed signature documents from the last week
Not supported: Does not handle document drafting, contract clause libraries, or payment collection - use for electronic signature workflows on prebuilt documents only.
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.
Install Jentic One Beta
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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feversign.com%2Feversign-e-signature-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feversign.com%2Feversign-e-signature-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
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
Patterns agents use Xodo Sign (Eversign) E-Signature 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
POST
/document_cancel
Cancel a pending document
POST
/document_trash
Move a document to trash
GET
/business
List businesses on the account
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
X
Xodo Sign (Eversign) E-Signature API
- Foundational (D)46/100
74
Foundational Compliance63
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability15
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
95%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
22%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
55%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Xodo Sign (Eversign) E-Signature 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 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.
GET STARTED