# Ignisign — how to use (mcp.ai)

Connect your Ignisign account and use 32 tools for e-signatures straight from your AI agent. Connect with your own API key. IgniSign is a comprehensive electronic signature platform that enables users to sign, send, and manage documents securely online.

## Option A — via MCP (recommended)
Remote MCP endpoint (HTTP, streamable): `https://api.mcp.ai/p_ignisign?ms=1787295840000`
Add it as a custom/remote MCP connector in your client (Claude, Cursor, VS Code…), then authenticate when prompted. Once connected, ask the agent to use the server's tools (e.g. `ignisign_api_authentication`).

## Option B — via direct REST API
Base URL: `https://api.mcp.ai/api/ignisign`
Auth: `Authorization: Bearer sk_live_…` — create a workspace API key at https://mcp.ai/settings/api-keys
Discover endpoints: `GET https://api.mcp.ai/api/ignisign/_endpoints`

### Endpoints
- `POST https://api.mcp.ai/api/ignisign/api/authentication` — Tool to authenticate an application over Ignisign API and retrieve a JWT. Use when obtaining a bearer token before making other API calls.
  - body: { appId: string, appEnv: string, secret: string }
- `POST https://api.mcp.ai/api/ignisign/cancel/signature/request` — Cancel (close) a signature request to terminate it. This uses the Ignisign /close endpoint which permanently cancels the signature workflow. Use this when you need to abort a signature request that is
  - body: { requestId: string }
- `POST https://api.mcp.ai/api/ignisign/create/document` — Tool to initialize a document for a signature request. Use when linking a new document to an existing signature request after creating that request.
  - body: { appId: string, label?: string, appEnv: string, externalId?: string, description?: string, signatureRequestId: string }
- `POST https://api.mcp.ai/api/ignisign/create/signer` — Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile.
  - body: { appId: string, email?: string, appEnv: string, lastName?: string, birthDate?: string, firstName?: string, birthPlace?: string, externalId?: string, nationality?: string, phoneNumber?: string, birthCountry?: string, signerProfileId: string }
- `POST https://api.mcp.ai/api/ignisign/create/webhook/endpoint` — Tool to create a new webhook endpoint for an application. Use after obtaining application ID and environment to register for event notifications.
  - body: { url: string, appId: string, appEnv: string, description?: string }
- `POST https://api.mcp.ai/api/ignisign/delete/document` — Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete.
  - body: { documentId: string }
- `POST https://api.mcp.ai/api/ignisign/delete/signature/request` — Permanently deletes a signature request from Ignisign by its ID. This action is irreversible and removes the signature request along with all associated data. The signature request ID can be obtained 
  - body: { signatureRequestId: string }
- `POST https://api.mcp.ai/api/ignisign/delete/signer` — Tool to revoke/delete a signer from an Ignisign application environment. This action permanently revokes the signer's access and is idempotent (can be called multiple times on the same signer). Use wh
  - body: { appId: string, appEnv: string, signerId: string }
- `POST https://api.mcp.ai/api/ignisign/delete/webhook/endpoint` — Delete a webhook endpoint by its ID. After deletion, returns the list of remaining webhook endpoints configured for the application environment. Use this tool when you need to remove a webhook that is
  - body: { webhookId: string }
- `POST https://api.mcp.ai/api/ignisign/get/application/context` — Tool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app.
  - body: { app_id: string }
- `POST https://api.mcp.ai/api/ignisign/get/document/information` — Tool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID.
  - body: { documentId: string }
- `POST https://api.mcp.ai/api/ignisign/get/missing/signer/inputs` — Tool to determine missing inputs needed for a signer in a specific signature profile. Use after selecting a signature profile and signer to identify required fields.
  - body: { appId: string, appEnv: string, signerId: string, signatureProfileId: string }
- `POST https://api.mcp.ai/api/ignisign/get/signature/request/details` — Tool to retrieve detailed information for a specific signature request. Use after creating or listing a signature request to inspect its details.
  - body: { signatureRequestId: string }
- `POST https://api.mcp.ai/api/ignisign/get/signature/request/document` — Tool to retrieve the document associated with a specific signature request. The action downloads the original file of a document. Provide `documentId` to select a specific document or omit to use the 
  - body: { requestId: string, documentId?: string }
- `POST https://api.mcp.ai/api/ignisign/get/signature/requests` — Retrieves a paginated list of signature requests for a specific Ignisign application and environment. Use this to list all signature requests (drafts, in-progress, completed, cancelled) in an applicat
  - body: { page?: integer, appId: string, appEnv: string, pageSize?: integer }
- `POST https://api.mcp.ai/api/ignisign/get/signed/document` — Tool to download the signed document (signature proof) for a signature request. The action will: 1) Resolve the first documentId from the signature request details. 2) Try v4: GET /documents/{document
  - body: { requestId: string }
- `POST https://api.mcp.ai/api/ignisign/get/signer/input/constraints` — Tool to get signer input constraints. Use when you need to know which fields are required from signers for a given signer profile.
  - body: { appId: string, appEnv: string, signerProfileId: string }
- `POST https://api.mcp.ai/api/ignisign/get/signer/inputs` — Retrieves the inputs provided by a specific signer for a signature request. Returns field values the signer has submitted (e.g., firstName, lastName, email). Use this after a signer has been added to 
  - body: { signerId: string, requestId: string }
- `POST https://api.mcp.ai/api/ignisign/get/signer/profile` — Retrieve detailed information about a specific signer profile by its ID. Use this to get profile settings including integration mode, authentication methods, and associated signers. First use 'Get Sig
  - body: { app_id: string, app_env: string, signer_profile_id: string }
- `POST https://api.mcp.ai/api/ignisign/get/signer/profiles` — Retrieve all signer profiles for a specific Ignisign application environment. Use this tool to list all configured signer profiles that define how signers interact with signature requests. Each profil
  - body: { app_id: string, app_env: string }
- `POST https://api.mcp.ai/api/ignisign/get/webhooks` — Retrieves all webhook endpoints configured for a specific Ignisign application environment. Returns the list of webhooks including their URLs, descriptions, and creation timestamps. Use this to audit 
  - body: { appId: string, appEnv: string }
- `POST https://api.mcp.ai/api/ignisign/init/signature/request` — Initialize a new signature request in Ignisign. This is the first step in creating a signature workflow. After initialization, you can add documents (IGNISIGN_CREATE_DOCUMENT), assign signers (IGNISIG
  - body: { appId: string, appEnv: string, signatureProfileId: string }
- `POST https://api.mcp.ai/api/ignisign/list/documents` — Tool to retrieve documents linked to a signature request. The action works by calling the signature request context endpoint and extracting its documentIds, then fetching each document detail.
  - body: { appId: string, appEnv: string, signatureRequestId: string }
- `POST https://api.mcp.ai/api/ignisign/provide/document/content/data/json` — Provides JSON content to an existing document in Ignisign. Use this action after creating a document with IGNISIGN_CREATE_DOCUMENT to attach structured JSON data that will be associated with a signatu
  - body: { documentId: string, jsonContent: object }
- `POST https://api.mcp.ai/api/ignisign/provide/document/content/file` — Tool to provide file content for a document. Use after creating a document to attach its file content.
  - body: { file: object, fileName?: string, mimeType?: string, documentId: string }
- `POST https://api.mcp.ai/api/ignisign/provide/document/content/private/file` — Provides private document content by submitting its SHA-256 hash to IgniSign. Use this after creating a document with IGNISIGN_CREATE_DOCUMENT when the document content should remain private (not uplo
  - body: { documentId: string, documentHash: string }
- `POST https://api.mcp.ai/api/ignisign/publish/signature/request` — Tool to publish a draft signature request. Use after adding all documents and signer details to the draft.
  - body: { signatureRequestId: string }
- `POST https://api.mcp.ai/api/ignisign/search/signers` — Tool to search for signers within an application environment with pagination support. Use after obtaining application ID and environment. Requires a non-empty filter string to search by name, email, o
  - body: { page?: integer, appId: string, appEnv: string, filter: string, pageSize?: integer }
- `POST https://api.mcp.ai/api/ignisign/update/document/information` — Tool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation.
  - body: { label?: string, documentId: string, externalId?: string, description?: string }
- `POST https://api.mcp.ai/api/ignisign/update/signature/request` — Tool to partially update a signature request in DRAFT state. Use when you need to modify draft request metadata before sending.
  - body: { title?: string, language?: string, signerIds?: string[], externalId?: string, statements?: object[], description?: string, documentIds?: string[], diffusionDate?: string, diffusionMode?: string, expirationDate?: string, signatureRequestId: string, expirationDateIsActivated?: boolean }
- `POST https://api.mcp.ai/api/ignisign/update/signer` — Updates an existing signer's profile assignment. Use this to change which signer profile a signer is associated with. The signer must already exist in the application environment. Requires: app_id (fr
  - body: { appId: string, appEnv: string, signerId: string, signerProfileId: string }
- `POST https://api.mcp.ai/api/ignisign/update/webhook/endpoint` — Tool to update an existing webhook endpoint. Use when you have a webhook ID and want to modify its destination URL or description. Example: Update the URL of webhook `68e7adc882353ea4e072bdbe` to `htt
  - body: { url: string, webhookId: string, description?: string }

## Example prompts
- "What can I do in Ignisign?"
- "Show me a summary of my Ignisign account"

## More
- Page: https://mcp.ai/ignisign
- Agent spec (llms.txt): https://mcp.ai/ignisign/llms.txt
- Postman collection: https://mcp.ai/ignisign/postman.json