Clicksign Envelope API

Name: Clicksign Envelope API API
Brand: Clicksign Envelope API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationapiKey44 EndpointsREST

For Agents

Assemble e-signature envelopes, attach documents, configure signatory requirements, and trigger notifications so agents can run document signing flows end to end.

Quickstart

Get started with Clicksign Envelope API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a document for signature"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Clicksign Envelope API API.

Create an envelope, attach PDF documents, and activate it for signing via POST /envelopes and POST /envelopes/{envelopeId}/activate

Add signatories to an envelope with configurable authentication requirements (email link, SMS token, selfie, ID upload)

Trigger reminder notifications to one or all signatories through /envelopes/{id}/notifications endpoints

Build reusable templates and organise envelopes into folders for high-volume signing operations

GET STARTED

Start building with Clicksign Envelope API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Clicksign Envelope API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Clicksign Envelope API, keeping it validated and agent-ready. Clicksign is a Brazilian electronic document signing platform; the v3 Envelope API exposes 44 endpoints for assembling envelopes, attaching one or more PDF documents, adding signatories with authentication requirements, sending notifications, and tracking signature progress through webhooks. Endpoints cover envelope CRUD, document upload, signatory and observer management, configurable signing requirements (email, SMS, selfie, ID document), templates, folders for organisation, and a WhatsApp-based acceptance flow popular in the Brazilian market. A sandbox base URL is provided for testing.

Use Cases

Patterns agents use Clicksign Envelope API API for, with concrete tasks.

★ Sales Contract Signing

Sales teams trigger envelope creation from CRM deal-closed events. The agent uploads the proposal PDF, adds signatories with email plus SMS authentication, and activates the envelope. Clicksign handles signer routing and audit trail. End-to-end automation closes the gap between deal and signed contract from days to under an hour.

Create an envelope, upload contract.pdf via POST /envelopes/{envelopeId}/documents, add a signatory with email authentication, and activate the envelope

High-Volume HR Onboarding

HR teams onboarding many new hires per week build a Clicksign template via POST /templates with offer letter and policy acknowledgements pre-mapped. Each new hire triggers an envelope from the template, stored in a per-quarter folder. Templates plus folders cut envelope assembly time from minutes per hire to seconds.

List templates with GET /templates, create an envelope from the offer-letter template, add the new hire as a signatory, and place it in folder ID 'q2-hires'

WhatsApp Acceptance Flow

For consumer-facing flows in Brazil, Clicksign supports a WhatsApp acceptance path so signatories accept terms through a WhatsApp message rather than email. This drives higher completion rates for short consumer contracts. The API configures the WhatsApp acceptance requirement on the envelope and notifications dispatch through Clicksign's WhatsApp integration.

Create a signatory with the WhatsApp acceptance requirement on an active envelope and trigger a notification

Agent-Driven Signature Orchestration

An AI agent assembles a custom contract on demand, requests signature, and reports progress back to a CRM. Through Jentic, the agent searches for 'send a document for signature', loads the envelope creation operation, and executes against credentials in the Jentic vault. The agent then polls envelope status or waits for a webhook callback before reporting completion.

Send NDA.pdf to legal@example.com for signature with email authentication, and return the envelope ID and signing URL

Key Endpoints

44 endpoints — jentic publishes the only available openapi specification for clicksign envelope api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/envelopes

Create an envelope

POST

/envelopes/{envelopeId}/documents

Upload a document into an envelope

POST

/envelopes/{envelopeId}/signers

Add a signatory to an envelope

POST

/envelopes/{envelopeId}/activate

Activate an envelope to start signing

POST

/envelopes/{envelopeId}/notifications

Notify all signatories of an envelope

POST

/templates

Create a reusable template

POST

/envelopes

Create an envelope

POST

/envelopes/{envelopeId}/documents

Upload a document into an envelope

POST

/envelopes/{envelopeId}/signers

Add a signatory to an envelope

POST

/envelopes/{envelopeId}/activate

Activate an envelope to start signing

POST

/envelopes/{envelopeId}/notifications

Notify all signatories of an envelope

Why though Jentic?

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

Credential isolation

Clicksign access tokens are stored encrypted in the Jentic vault. Agents receive scoped tokens and never see the raw Authorization value.

Intent-based discovery

Agents search Jentic with intents like 'send a document for signature' or 'add a signatory to a contract' and Jentic returns the matching Clicksign operations with their input schemas.

Time to first call

Direct Clicksign integration: 2-3 days for auth, envelope assembly, signer rules, and webhook handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Clicksign (developer docs)

Companion specification published from Clicksign's developer docs for the same e-signature platform.

Use this when an agent needs the developer-docs surface; choose the main Envelope API spec when working from the v3 production endpoints.

Complementary

ClickSend

ClickSend dispatches SMS or email reminders pointing recipients at Clicksign signing URLs.

Pair when the agent needs to push out reminder messaging on a separate channel from the built-in Clicksign notifications.

Complementary

Clientary

Clientary issues invoices that can be paired with a Clicksign-signed agreement.

Pair when an agent needs to send a signed contract through Clicksign and follow it with a Clientary invoice.

FAQs

Specific to using Clicksign Envelope API API through Jentic.

Why is there no official OpenAPI spec for Clicksign Envelope API?

Clicksign does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clicksign Envelope 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 Clicksign Envelope API use?

The Clicksign Envelope API uses an access token sent in the Authorization header. Tokens are generated by the account administrator in the Clicksign dashboard. Through Jentic, the token is stored encrypted in the vault and injected at execution time so agents never see the raw value.

Can I add multiple documents to a single envelope with the Clicksign API?

Yes. POST /envelopes/{envelopeId}/documents uploads a PDF into an existing envelope; you can call it repeatedly to attach as many documents as required before activating the envelope with POST /envelopes/{envelopeId}/activate.

What are the rate limits for the Clicksign Envelope API?

Rate limits are not declared in the OpenAPI spec. Clicksign applies plan-tier limits visible in your account settings — confirm them before issuing high-volume envelope creation. Through Jentic, rate-limit responses surface as standard error objects an agent can retry against.

How do I send a contract for signature through the Clicksign API via Jentic?

Run pip install jentic, then search Jentic for 'send a document for signature' to find POST /envelopes. Load the operation schema, supply the envelope payload, then upload documents via POST /envelopes/{envelopeId}/documents, add signers, and activate. Jentic injects the Authorization token from the vault.

Is there a sandbox environment for testing Clicksign envelopes?

Yes. The spec lists https://sandbox.clicksign.com/api/v3 as the sandbox server alongside the production base URL. Use the sandbox while wiring up envelope creation, signatory rules, and webhook handling before switching to production credentials.