Clicksign API

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

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationapiKey12 EndpointsREST

For Agents

Create signing documents, add signers, link them via signature lists, and dispatch notifications so agents can run lightweight document signing flows.

Quickstart

Get started with Clicksign 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:
"create a document for signature"

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

Capabilities

What an agent can do with Clicksign API API.

Create a document for signature via POST /documents and pull its signing status with GET /documents/{key}

Cancel a pending document with DELETE /documents/{key} when an agreement is no longer needed

Trigger a manual notification to a signer through POST /notifications

GET STARTED

Start building with Clicksign API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Clicksign API, keeping it validated and agent-ready. This is the v1 surface of Clicksign's electronic document signing platform — the lighter, document-centric predecessor of the v3 envelope model. The 12 endpoints cover document creation, signer registration, signature list assembly that connects signers to documents, manual notification dispatch, and webhook subscription. Authentication uses an access_token query parameter, and a sandbox base URL is provided for testing before promoting to production.

Use Cases

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

★ Lightweight Document Signing

Teams that only need a single document signed by one or two parties use the v1 API to upload the document, register signers via POST /signers, attach them through POST /lists, and watch for completion via webhook. The minimal endpoint surface keeps the integration small for use cases that do not need v3's envelope grouping.

Create a document with a PDF attachment, add a signer with email auth via POST /lists, and return the signing URL

Webhook-Driven Status Tracking

Rather than poll, applications register webhooks via POST /webhooks for signing lifecycle events and react when documents are signed, refused, or cancelled. The agent or downstream system updates its own state from the webhook payload — no scheduled GET /documents/{key} polling required.

Create a webhook subscribed to document signed events pointing at https://example.com/clicksign/hook and verify it appears in GET /webhooks

Reminder Notifications

When a signer has not opened the signing link, the agent triggers a manual reminder via POST /notifications. This is paired with cancellation logic — if no signature within an SLA window, DELETE /documents/{key} closes the document. The combination keeps signing flows from leaving documents indefinitely pending.

Send a notification to the signer linked to a specific document and confirm the response indicates the notification was queued

Agent-Driven Signing Loop

An AI agent in a contracts platform creates a document, attaches signers, monitors webhooks, and reports signed status to the calling system. Through Jentic, the agent searches for 'create a document for signature', loads the operation, and executes against credentials in the Jentic vault. End-to-end integration time is under an hour.

Create a document, add signer alice@example.com to its signature list, send a notification, and return the document key for tracking

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/documents

Create a signing document

POST

/signers

POST

/lists

Link a signer to a document

POST

/notifications

Send a manual notification to a signer

POST

/webhooks

Subscribe to signing events

DELETE

/documents/{key}

Cancel a pending document

POST

/documents

Create a signing document

POST

/signers

POST

/lists

Link a signer to a document

POST

/notifications

Send a manual notification to a signer

POST

/webhooks

Subscribe to signing events

DELETE

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 access_token query parameter value.

Intent-based discovery

Agents search Jentic with intents like 'create a document for signature' or 'send a signing reminder' and Jentic returns the matching Clicksign v1 operations with their input schemas.

Time to first call

Direct Clicksign v1 integration: 1-2 days for auth, document creation, signer linking, and webhook handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Clicksign Envelope API (v3)

Newer envelope-based API from the same vendor with 44 endpoints, richer auth requirements, and template support.

Choose the v3 envelope API when an agent needs multi-document envelopes, selfie or ID auth, templates, or WhatsApp acceptance flows.

Complementary

ClickSend

ClickSend dispatches SMS or email reminders containing the Clicksign signing URL.

Pair when an agent needs reminder messaging on a different 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 up with a Clientary invoice.

FAQs

Specific to using Clicksign API API through Jentic.

Why is there no official OpenAPI spec for Clicksign API?

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

The Clicksign v1 API uses an access token sent as the access_token query parameter on every request. The token is generated in the Clicksign dashboard. Through Jentic, the token is stored encrypted in the vault and appended to requests at execution time so agents never see the raw value.

Can I link a signer to a specific document with the Clicksign API?

Yes. POST /signers registers the person, and POST /lists creates the relationship between a signer and a document. To remove the link, call DELETE /lists/{list_key}. This two-step pattern lets you reuse a signer record across multiple documents.

What are the rate limits for the Clicksign API?

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

How do I subscribe to signature completion events through Jentic?

Run pip install jentic, then search Jentic for 'subscribe to signature completion events' to find POST /webhooks. Load the operation, supply the callback URL and event types, and execute. Jentic injects the access_token query parameter from the vault.

Should I use the v1 Clicksign API or the v3 Envelope API?

The v1 API is document-centric and minimal — 12 endpoints suited to single-document flows. The v3 Envelope API groups documents and signatories into envelopes with richer authentication requirements (selfie, ID upload, WhatsApp acceptance). Choose v1 for lightweight single-document automations and v3 for multi-document, high-assurance signing.