canonical: https://jentic.com/apis/ignisign.io/ignisign

# IgniSign API

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.

## For AI agents

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

## Scope

Does not handle document drafting, payment collection, or full CLM workflows - use for electronic signature, signer management, and signature proofs only.

## Capabilities

- 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
- Issue electronic seals and bare signatures for non-eIDAS workflows

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Signers** — Create, update, retrieve, and revoke signer profiles.
- **Signature Requests** — Send documents for signature and check signing status.
- **Signature Proofs** — Retrieve cryptographic proofs for completed signatures.
- **Application Invitations** — Invite, edit, resend, and cancel application user invitations.
- **Webhooks** — Subscribe to signing lifecycle events.

## Why Jentic

- **Setup:** Wiring IgniSign by hand means setting up its bearer auth against api.ignisign.io and managing the signer and application lifecycle yourself. Through Jentic you install once, import the IgniSign API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** IgniSign puts the signer id and application id in the URL path (`/signers/{signerId}`, `/applications/{appId}/invitations`), so a rule can pin your agent to one signer or application. You choose the operations it may call, so destructive ones like deleting a signer are not included unless you add them.
- **Credential handling:** Your IgniSign bearer token 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.
- **Discovery method:** Agents search Jentic by intent such as 'send a document for signature' or 'get a signer summary', and Jentic returns the matching IgniSign operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **PandaDoc API** — PandaDoc is a US-centric alternative for document workflows and signatures with templating built in.
- **SignWell API** — SignWell offers simpler eSignature workflows at a lower price point.
- **Stripe API** — Stripe charges the customer once the contract is signed.

## FAQ

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

### Can I limit what my agent is allowed to do with the IgniSign API?

Yes. Because you self-host Jentic One, your own rules decide which IgniSign operations and credentials the agent may use. IgniSign carries the signer id and application id in the path, as in `/signers/{signerId}` and `/applications/{appId}/invitations`, so you can pin the agent to a single signer or application. You also choose the exact operations it may call, so destructive ones like DELETE `/signers/{signerId}` stay excluded unless you add them.