IgniSign API

Name: IgniSign API API
Brand: IgniSign API
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationbearer41 EndpointsREST

For Agents

Send documents for electronic signature, manage signers, and retrieve signature proofs and webhooks through IgniSign's eIDAS-compliant signing platform.

Quickstart

Get started with IgniSign 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 electronic signature"

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

Capabilities

What an agent can do with IgniSign API API.

Create or update a signer profile via POST /signers

Send a signature request with one or more documents to a signer

Retrieve cryptographic signature proofs for completed signatures

Manage application invitations to bring new users into the application

Configure webhooks to receive signature lifecycle events

GET STARTED

Start building with IgniSign API API

Explore with Jentic

View OpenAPI Document

IgniSign is an electronic signature platform that supports document signing, signer management, signature requests, signature proofs, webhooks, electronic seals, and bare signatures. The /v4 API exposes operations to invite users to an application, create and manage signers, build signature requests with attached documents, retrieve cryptographic signature proofs, and orchestrate webhooks for status events. It supports advanced and qualified electronic signature levels suited to regulated workflows in EU eIDAS contexts.

Use Cases

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

★ Contract Signing for SaaS Onboarding

Send service agreements, NDAs, and order forms for electronic signature during SaaS or B2B onboarding. Create the signer with POST /signers, then attach the document to a signature request and let IgniSign route it to the signer's email. Webhooks notify the back-office system when the signature completes, and POST /signers/{signerId}/details fetches the captured proof.

Create a signer for 'jane@example.com' via POST /signers, attach contract.pdf to a new signature request, and wait for the webhook to confirm completion.

Compliant eIDAS Signature Capture

Capture qualified electronic signatures (QES) for regulated documents in EU jurisdictions where eIDAS applies. IgniSign generates a tamper-evident signature proof retrievable via GET /signers/{signerId}/summary that compliance teams can archive alongside the signed document for legal admissibility.

Retrieve the signer summary after signature completion and store the proof reference in the corporate document management system.

Multi-User Application Management

Onboard internal users to an IgniSign application via the invitations endpoints — POST /applications/{appId}/invitations creates an invite, PATCH amends it, and POST /resend re-issues it. Suitable for agencies, law firms, and shared HR portals where multiple staff members issue signature requests.

Invite three new users to application 'app-001' and confirm they have accepted the invitation.

AI Agent Contract Workflow

An AI agent in a procurement or HR workflow drafts a contract, locates the right signer, sends it for signature through IgniSign, and writes the proof reference back to the source system on completion. Through Jentic the agent finds the IgniSign request operation in one search, with credentials kept in the vault.

Use Jentic to call POST /signers and create a signer, then send a signature request and listen for the webhook callback.

Key Endpoints

41 endpoints — ignisign is an electronic signature platform that supports document signing, signer management, signature requests, signature proofs, webhooks, electronic seals, and bare signatures.

METHOD

PATH

DESCRIPTION

POST

/signers

Create or update a signer

GET

/signers/{signerId}

Get a signer by ID

GET

/signers/{signerId}/summary

Get signer summary including signature proof

PUT

/signers/{signerId}

Update a signer

DELETE

/signers/{signerId}

Revoke a signer

POST

/applications/{appId}/invitations

Invite a new application user

GET

/applications/{appId}/context

Get application context

POST

/signers

Create or update a signer

GET

/signers/{signerId}

Get a signer by ID

GET

/signers/{signerId}/summary

Get signer summary including signature proof

PUT

/signers/{signerId}

Update a signer

DELETE

/signers/{signerId}

Revoke a signer

Why though Jentic?

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

Credential isolation

IgniSign Bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access only — the raw token never enters the agent's context window.

Intent-based discovery

Agents search by intent (e.g., 'send a document for signature') and Jentic returns the matching IgniSign operation with its input schema.

Time to first call

Direct IgniSign integration: 2-4 days for auth, signer creation, webhook handling, and proof retrieval. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PandaDoc API

PandaDoc is a US-centric alternative for document workflows and signatures with templating built in.

Choose PandaDoc for proposal templating and US-market workflows; choose IgniSign for eIDAS qualified signatures in the EU.

Alternative

SignWell API

SignWell offers simpler eSignature workflows at a lower price point.

Choose SignWell when basic e-signature suffices; IgniSign when EU regulatory levels (AES, QES) are required.

Complementary

Stripe API

Stripe charges the customer once the contract is signed.

Pair IgniSign with Stripe in onboarding flows: collect the signed contract first, then charge the customer's payment method.

FAQs

Specific to using IgniSign API API through Jentic.

What authentication does the IgniSign API use?

IgniSign uses Bearer token authentication. Through Jentic, the token is stored in the vault and injected at execution time, so the agent never sees the raw secret.

Can I send a document for electronic signature with the IgniSign API?

Yes. Create a signer with POST /signers, then attach the document to a signature request. Webhooks notify your system on each lifecycle change, and proofs are retrievable from the signer endpoints.

Does the IgniSign API support eIDAS qualified signatures?

Yes. IgniSign supports advanced and qualified electronic signature levels per eIDAS, with cryptographic proofs returned via the signer summary and details endpoints for legal archival.

What are the rate limits for the IgniSign API?

Rate limits are not declared in the OpenAPI spec; IgniSign enforces plan-tier throttles per application. Handle 429 responses with exponential backoff and contact support for higher quotas.

How do I receive notifications when a document is signed?

Configure a webhook through the application's webhook endpoints. IgniSign POSTs lifecycle events (created, signed, completed, expired) to your URL so the agent does not need to poll.

How do I send a document for signature through Jentic?

Run pip install jentic, search 'send a document for electronic signature', load the schema for the IgniSign signature request operation, and execute with the document and signer details.