Can an agent download the finished signed document?

Yes. Every variant supports downloading the final signed PDF once all parties have signed. The xodosign variant additionally returns the raw unsigned source document, which is useful for audit trails that need both the original and executed versions.

Do these APIs generate or draft the documents themselves?

No. Xodo Sign handles the signature workflow on documents you already have or have saved as templates. Document drafting, clause libraries, proposal authoring, pricing tables, and payment collection are outside the scope of these APIs.

Xodo Sign (eversign) APIs for AI Agents

Q: Can agents send the same document to many signers at once?

Yes. The xodosign variant exposes template bulk-CSV jobs: fetch a blank CSV for a template, populate one row per recipient, and submit the bulk job to send a personalised signature request per row. The other variants can reuse templates one recipient at a time from the document endpoint.

ProductivityCollaborationJentic-Generated SpecsAPI keyAgent Ready

www.xodosign.com·Developer portal → xodo-sign.readme.io

Xodo Sign (eversign) API Catalog

3 APIs across 1 product group. All share one credential.

Productivity3

Xodo Sign (Eversign) E-Signature APISend documents for signature, manage templates, and orchestrate bulk-signing flows on Xodo Sign (formerly eversign), with full lifecycle tracking from creation to signed PDF.~17 endpoints Xodo Sign APIRun high-volume Xodo Sign signing pipelines with template bulk-CSV jobs, file uploads, and raw or final document downloads.~11 endpoints Xodo Sign (eversign) APISend and track signature documents through Xodo Sign using clean hash-addressed endpoints, including cancel, reminder, and final-PDF download.~9 endpoints

Which Xodo Sign (eversign) API should I use?

I want to...	Use	Why
Full document lifecycle with signer reassignment, trash, and multi-business switching	Xodo Sign (Eversign) E-Signature API	The 17-endpoint surface adds reassign_signer, document_trash, and business switching beyond basic send and track.
Clean REST paths where each document is addressed by a hash in the URL	Xodo Sign (eversign) API	This 9-endpoint variant uses path-style /document/{document_hash} operations instead of query-string parameters.
High-volume bulk signing from a template plus file attachments	Xodo Sign API	This 11-endpoint variant exposes template bulk-CSV jobs and a /file upload endpoint the other variants lack.

Install Jentic One Beta

Connect the Xodo Sign (eversign) APIs to your agent

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Xodo Sign by hand means passing your API key on the api.eversign.com host and coding the document, template, reminder, and download calls for each variant yourself. With Jentic you install Jentic One once, add the Xodo Sign APIs from the Jentic directory, store the key once, and your agent calls any variant.

Permission scoping

You choose which Xodo Sign operations the agent may call through your own Jentic One rules, so destructive ones like cancelling or trashing a document are excluded unless you add them. Because the hash variant carries the document hash in the URL path, a rule can pin an agent to a single document for reading, reminders, and final-PDF download.

Credential isolation

FAQs

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

What is the difference between the three Xodo Sign APIs listed here?

They are three OpenAPI specs for the same Xodo Sign (eversign) platform that differ in addressing and reach. The E-Signature API is a 17-endpoint surface with the fullest lifecycle controls including signer reassignment, trash, and multi-business switching. The xodo-sign variant is a 9-endpoint REST surface that addresses each document by a hash in the URL path. The xodosign variant is an 11-endpoint surface built around template bulk-CSV jobs and file uploads.

Which Xodo Sign API should an agent start with?

Start with the E-Signature API if you want the broadest lifecycle coverage in one place. Choose the xodo-sign variant if you prefer clean path-style document hashes over query-string parameters. Choose the xodosign variant when you need high-volume bulk signing from a template or need to attach uploaded files to documents.

Is one Xodo Sign API key enough for all three variants?

Yes. Every variant authenticates with the same apiKey credential against the api.eversign.com host, so a single Xodo Sign key works across all three. The endpoints and base paths differ, but the credential does not.

Can agents send the same document to many signers at once?

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo

For Agents

APIs3 in catalogue

Endpoints37 indexed

AuthAPI key — 1 credential for all 3 APIs

ProvenanceJentic-generated specs

An agent can send documents for electronic signature, manage reusable templates, dispatch template bulk-CSV signing jobs, remind or reassign signers, cancel or trash in-flight documents, and download raw or final signed PDFs across the Xodo Sign API variants.

Xodo Sign (eversign) is an e-signature platform whose API is offered here as three overlapping specs that differ mainly in endpoint addressing and reach: query-style lifecycle management, clean hash-addressed REST paths, and a bulk-CSV signing surface with file uploads. Agents can pick the variant that matches how they want to address documents and whether they need high-volume bulk sending.

Use for: Sending documents for electronic signature, managing reusable templates, running template bulk-signing jobs, reminding or reassigning signers, and downloading raw or final signed PDFs on Xodo Sign (eversign).

Not supported: document drafting, contract clause libraries, proposal authoring, pricing tables, payment collection

Credentials: All three Xodo Sign API variants use a single apiKey credential against the api.eversign.com host, so one Xodo Sign API key covers every variant.

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" | sh

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

What AI Agents Can Do with Xodo Sign (eversign)

Each workflow spans multiple Xodo Sign (eversign) APIs. Jentic routes each operation to the right API automatically.

Template bulk send with a signed-PDF archive

Dispatch the same NDA or vendor agreement to many recipients from a template bulk-CSV job, then archive each executed contract as it completes. The bulk variant handles the high-volume dispatch while the lifecycle variant filters and tracks documents through to completion.

Example prompt:

Fetch the blank CSV via GET /template/{template_hash}/bulk/csv/blank on the bulk variant, populate recipient rows and POST the bulk job, then poll the lifecycle variant for completed documents and download each final PDF

APIs used

Xodo Sign API + Xodo Sign (Eversign) E-Signature API

Send by template, then track and cancel stale documents

Create signature requests from a reusable template and monitor them by status, cancelling anything left pending past a deadline. Hash-addressed paths give a clean handle on each document while the wider lifecycle surface supplies cancel and trash operations.

Example prompt:

POST /document on the hash variant and capture each document_hash, then on the lifecycle variant list documents pending over 30 days and call /document_cancel for each

APIs used

Xodo Sign (eversign) API + Xodo Sign (Eversign) E-Signature API

Attach an exhibit, send, and download the signed PDF by hash

Upload a PDF exhibit, include it when creating a signature document, and retrieve the completed PDF once all parties sign. File upload comes from the bulk variant while the hash-addressed variant gives a clean path for the final-PDF download.

Example prompt:

POST /file on the bulk variant to register the exhibit, POST /document referencing the file_id, then GET /document/{document_hash}/download_final_pdf on the hash variant once status is completed

APIs used

Xodo Sign API + Xodo Sign (eversign) API

Xodo Sign (eversign) APIs for AI Agents

Xodo Sign (eversign) API Catalog

Productivity3

Which Xodo Sign (eversign) API should I use?

Connect the Xodo Sign (eversign) APIs to your agent

Why Jentic?

FAQs

Start Connecting APIs to Your AI Agents

What AI Agents Can Do with Xodo Sign (eversign)

If you need a different Productivity vendor