# Ignisign

```json
{
  "name": "Ignisign",
  "slug": "ignisign",
  "url": "https://composio.dev/toolkits/ignisign",
  "markdown_url": "https://composio.dev/toolkits/ignisign.md",
  "logo_url": "https://ignisign.io/logo.png",
  "categories": [
    "document & file management"
  ],
  "is_composio_managed": false,
  "updated_at": "2026-05-12T10:15:40.413Z"
}
```

![Ignisign logo](https://ignisign.io/logo.png)

## Description

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Ignisign MCP or direct API to sign documents, send signature requests, manage templates, and track signing status through natural language.

## Summary

Ignisign is an electronic signature platform for secure online document signing and management. Streamline agreements and digital paperwork with advanced workflow tools.

## Categories

- document & file management

## Toolkit Details

- Tools: 32

## Images

- Logo: https://ignisign.io/logo.png

## Authentication

- **Api Key**
  - Type: `api_key`
  - Description: Api Key authentication for Ignisign.
  - Setup:
    - Configure Api Key credentials for Ignisign.
    - Use the credentials when creating an auth config in Composio.

## Suggested Prompts

- Start a new signature request for a contract
- Add a new signer to this application
- Delete a completed document by its ID
- Create a webhook to track signature events

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `IGNISIGN_API_AUTHENTICATION` | 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. |
| `IGNISIGN_CANCEL_SIGNATURE_REQUEST` | 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 in DRAFT or IN_PROGRESS status. This operation is idempotent - calling it on an already cancelled request returns success without error. |
| `IGNISIGN_CREATE_DOCUMENT` | Initialize 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. |
| `IGNISIGN_CREATE_SIGNER` | Create Signer | Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile. |
| `IGNISIGN_CREATE_WEBHOOK_ENDPOINT` | 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. |
| `IGNISIGN_DELETE_DOCUMENT` | Delete Document | Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete. |
| `IGNISIGN_DELETE_SIGNATURE_REQUEST` | Delete Ignisign 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 from the IGNISIGN_INIT_SIGNATURE_REQUEST action or IGNISIGN_GET_SIGNATURE_REQUESTS action. |
| `IGNISIGN_DELETE_SIGNER` | 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 when you need to remove a signer after confirming their signer ID. |
| `IGNISIGN_DELETE_WEBHOOK_ENDPOINT` | 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 no longer needed or to clean up unused webhooks. The webhook ID can be obtained from the create webhook or list webhooks endpoints. |
| `IGNISIGN_GET_APPLICATION_CONTEXT` | Get application context | Tool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app. |
| `IGNISIGN_GET_DOCUMENT_INFORMATION` | Get Document Information | Tool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID. |
| `IGNISIGN_GET_MISSING_SIGNER_INPUTS` | 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. |
| `IGNISIGN_GET_SIGNATURE_REQUEST_DETAILS` | 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. |
| `IGNISIGN_GET_SIGNATURE_REQUEST_DOCUMENT` | 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 first available document of the request. |
| `IGNISIGN_GET_SIGNATURE_REQUESTS` | 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 application. Each signature request can have associated documents and signers. Returns pagination metadata to iterate through large result sets. Note: The app_env parameter must match your API key's environment scope. |
| `IGNISIGN_GET_SIGNED_DOCUMENT` | 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/{documentId}/signatures/PDF_WITH_SIGNATURES 3) Fallback v3: GET /v3/documents/{documentId}/signature-proof 4) Final fallback: GET /documents/{documentId}/file (original file) |
| `IGNISIGN_GET_SIGNER_INPUT_CONSTRAINTS` | 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. |
| `IGNISIGN_GET_SIGNER_INPUTS` | 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 a signature request to fetch their profile information. The signer must be associated with the specified signature request. |
| `IGNISIGN_GET_SIGNER_PROFILE` | 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 Signer Profiles' to list available profile IDs. |
| `IGNISIGN_GET_SIGNER_PROFILES` | 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 profile specifies integration mode (BY_SIDE, EMBEDDED, or MACHINE_TO_MACHINE), authentication methods, and other settings. Returns profile IDs which can be used when creating signers or signature requests. |
| `IGNISIGN_GET_WEBHOOKS` | 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 existing webhook integrations or verify webhook configurations. |
| `IGNISIGN_INIT_SIGNATURE_REQUEST` | Initialize Ignisign 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 (IGNISIGN_CREATE_SIGNER), and publish the request (IGNISIGN_PUBLISH_SIGNATURE_REQUEST) to start the signing process. |
| `IGNISIGN_LIST_DOCUMENTS` | 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. |
| `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_DATA_JSON` | 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 signature request. The JSON content is stored and can be used for document generation or data binding in signature workflows. |
| `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_FILE` | Provide Document Content File | Tool to provide file content for a document. Use after creating a document to attach its file content. |
| `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_PRIVATE_FILE` | 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 uploaded). The hash proves document integrity without exposing its contents. The document status will change to 'PROVIDED' upon success. |
| `IGNISIGN_PUBLISH_SIGNATURE_REQUEST` | Publish Signature Request | Tool to publish a draft signature request. Use after adding all documents and signer details to the draft. |
| `IGNISIGN_SEARCH_SIGNERS` | 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, or external ID. Use '*' to match all signers. Supports page and pageSize parameters to paginate through large result sets. |
| `IGNISIGN_UPDATE_DOCUMENT_INFORMATION` | Update Document Information | Tool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation. |
| `IGNISIGN_UPDATE_SIGNATURE_REQUEST` | Update Signature Request | Tool to partially update a signature request in DRAFT state. Use when you need to modify draft request metadata before sending. |
| `IGNISIGN_UPDATE_SIGNER` | 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 (from Get Application Context), signer_id (from Create Signer or Search Signers), and signer_profile_id (from Get Signer Profiles). |
| `IGNISIGN_UPDATE_WEBHOOK_ENDPOINT` | 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 `https://example.com/webhook`. |

## Supported Triggers

None listed.

## Installation and MCP Setup

### Path 1: SDK Installation

#### Path 1, Step 1: Install Composio

Install the Composio SDK
```python
pip install composio_openai
```

```typescript
npm install @composio/openai
```

#### Path 1, Step 2: Initialize Composio and Create Tool Router Session

Import and initialize Composio client, then create a Tool Router session
```python
from openai import OpenAI
from composio import Composio
from composio_openai import OpenAIResponsesProvider

composio = Composio(provider=OpenAIResponsesProvider())
openai = OpenAI()
session = composio.create(user_id='your-user-id')
```

```typescript
import OpenAI from 'openai';
import { Composio } from '@composio/core';
import { OpenAIResponsesProvider } from '@composio/openai';

const composio = new Composio({
  provider: new OpenAIResponsesProvider(),
});
const openai = new OpenAI({});
const session = await composio.create('your-user-id');
```

#### Path 1, Step 3: Execute Ignisign Tools via Tool Router with Your Agent

Get tools from Tool Router session and execute Ignisign actions with your Agent
```python
tools = session.tools
response = openai.responses.create(
  model='gpt-4.1',
  tools=tools,
  input=[{
    'role': 'user',
    'content': 'Send a contract for signature to a new client'
  }]
)
result = composio.provider.handle_tool_calls(
  response=response,
  user_id='your-user-id'
)
print(result)
```

```typescript
const tools = session.tools;
const response = await openai.responses.create({
  model: 'gpt-4.1',
  tools: tools,
  input: [{
    role: 'user',
    content: 'Send a contract for signature to a new client'
  }],
});
const result = await composio.provider.handleToolCalls(
  'your-user-id',
  response.output
);
console.log(result);
```

### Path 2: MCP Server Setup

#### Path 2, Step 1: Install Composio

Install the Composio SDK and Claude Agent SDK
```python
pip install composio claude-agent-sdk
```

```typescript
npm install @composio/core ai @ai-sdk/openai @ai-sdk/mcp
```

#### Path 2, Step 2: Create Tool Router Session

Initialize the Composio client and create a Tool Router session
```python
from composio import Composio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions

composio = Composio(api_key='your-composio-api-key')
session = composio.create(user_id='your-user-id')
url = session.mcp.url
```

```typescript
import { Composio } from '@composio/core';

const composio = new Composio({ apiKey: 'your-api-key' });

console.log("Creating Tool Router session...");
const { mcp } = await composio.create('your-user-id');
console.log(`Tool Router session created: ${mcp.url}`);
```

#### Path 2, Step 3: Connect to AI Agent

Use the MCP server with your AI agent
```python
import asyncio

options = ClaudeAgentOptions(
    permission_mode='bypassPermissions',
    mcp_servers={
        'tool_router': {
            'type': 'http',
            'url': url,
            'headers': {
                'x-api-key': 'your-composio-api-key'
            }
        }
    },
    system_prompt='You are a helpful assistant with access to Ignisign tools.',
    max_turns=10
)

async def main():
    async with ClaudeSDKClient(options=options) as client:
        await client.query('Send signature request to alice@example.com for NDA.pdf')
        async for message in client.receive_response():
            if hasattr(message, 'content'):
                for block in message.content:
                    if hasattr(block, 'text'):
                        print(block.text)

asyncio.run(main())
```

```typescript
import { openai } from '@ai-sdk/openai';
import { experimental_createMCPClient as createMCPClient } from '@ai-sdk/mcp';
import { generateText, stepCountIs } from 'ai';

const client = await createMCPClient({
  transport: {
    type: 'http',
    url: mcp.url,
    headers: { 'x-api-key': 'your-composio-api-key' }
  }
});

const tools = await client.tools();

const { text } = await generateText({
  model: openai('gpt-4o'),
  tools,
  messages: [{ role: 'user', content: 'Send signature request to alice@example.com for NDA.pdf' }],
  stopWhen: stepCountIs( 5 )
});

console.log(`Agent: ${text}`);
```

## Why Use Composio?

### 1. AI Native Ignisign Integration

- Supports both Ignisign MCP and direct API based integrations
- Structured, LLM-friendly schemas for reliable tool execution
- Rich coverage for reading, writing, and querying your Ignisign data

### 2. Managed Auth

- Built-in API key management with secure token storage
- Central place to manage, scope, and revoke Ignisign access
- Per user and per environment credentials instead of hard-coded keys

### 3. Agent Optimized Design

- Tools are tuned using real error and success rates to improve reliability over time
- Comprehensive execution logs so you always know what ran, when, and on whose behalf

### 4. Enterprise Grade Security

- Fine-grained RBAC so you control which agents and users can access Ignisign
- Scoped, least privilege access to Ignisign resources
- Full audit trail of agent actions to support review and compliance

## Use Ignisign with any AI Agent Framework

Choose a framework you want to connect Ignisign with:

- [OpenAI Agents SDK](https://composio.dev/toolkits/ignisign/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/ignisign/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/ignisign/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/ignisign/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/ignisign/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/ignisign/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/ignisign/framework/hermes-agent)
- [Google ADK](https://composio.dev/toolkits/ignisign/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/ignisign/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/ignisign/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/ignisign/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/ignisign/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/ignisign/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/ignisign/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/ignisign/framework/autogen)

## Related Toolkits

- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.
- [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.
- [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.
- [Affinda](https://composio.dev/toolkits/affinda) - Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data.
- [Agility cms](https://composio.dev/toolkits/agility_cms) - Agility CMS is a headless content management system for building and managing digital experiences across platforms. It lets teams update content quickly and deliver omnichannel experiences with ease.
- [Algodocs](https://composio.dev/toolkits/algodocs) - Algodocs is an AI-powered platform that automates data extraction from business documents. It delivers fast, secure, and accurate processing without templates or manual training.
- [Api2pdf](https://composio.dev/toolkits/api2pdf) - Api2Pdf is a REST API for generating PDFs from HTML, URLs, and documents using powerful engines like wkhtmltopdf and Headless Chrome. It streamlines document conversion and automation for developers and businesses.
- [Aryn](https://composio.dev/toolkits/aryn) - Aryn is an AI-powered platform for parsing, extracting, and analyzing data from unstructured documents. Use it to automate document processing and unlock actionable insights from your files.
- [Boldsign](https://composio.dev/toolkits/boldsign) - Boldsign is a digital eSignature platform for sending, signing, and tracking documents online. Organizations use it to automate agreements and manage legally binding workflows efficiently.
- [Boloforms](https://composio.dev/toolkits/boloforms) - BoloForms is an eSignature platform built for small businesses, offering unlimited signatures, templates, and forms. It simplifies digital document signing and team collaboration at a predictable, fixed price.
- [Box](https://composio.dev/toolkits/box) - Box is a cloud content management and file sharing platform for businesses. It helps teams securely store, organize, and collaborate on files from anywhere.
- [Carbone](https://composio.dev/toolkits/carbone) - Carbone is a blazing-fast report generator that turns JSON data into PDFs, Word docs, spreadsheets, and more using flexible templates. It lets you automate document creation at scale with minimal code.
- [Castingwords](https://composio.dev/toolkits/castingwords) - CastingWords is a transcription service specializing in human-powered, accurate transcripts via a simple API. Get seamless audio-to-text conversion for interviews, meetings, podcasts, and more.
- [Cloudconvert](https://composio.dev/toolkits/cloudconvert) - CloudConvert is a powerful file conversion service supporting over 200 file formats. It streamlines converting, compressing, and managing documents, media, and more, all in one place.
- [Cloudlayer](https://composio.dev/toolkits/cloudlayer) - Cloudlayer is a document and asset generation service for creating PDFs and images via API or SDKs. It lets you automate high-quality doc creation, saving dev time and reducing manual work.
- [Cloudpress](https://composio.dev/toolkits/cloudpress) - Cloudpress is a content export tool for Google Docs and Notion. It automates publishing to your favorite Content Management Systems.
- [Contentful graphql](https://composio.dev/toolkits/contentful_graphql) - Contentful graphql is a content delivery API that lets you access Contentful data using GraphQL queries. It gives you efficient, flexible ways to fetch and manage structured content for any digital project.
- [Conversion tools](https://composio.dev/toolkits/conversion_tools) - Conversion Tools is an online service for converting documents between formats such as PDF, Word, Excel, XML, and CSV. It lets you automate complex document workflows with just a few clicks.
- [Convertapi](https://composio.dev/toolkits/convertapi) - ConvertAPI is a robust file conversion service for documents, images, and spreadsheets. It streamlines programmatic format changes and lets developers automate complex workflows with a single API.
- [Craftmypdf](https://composio.dev/toolkits/craftmypdf) - CraftMyPDF is a web-based service for designing and generating PDFs with templates and live data. It streamlines document creation by automating personalized PDFs at scale.

## Frequently Asked Questions

### Do I need my own developer credentials to use Ignisign with Composio?

Yes, Ignisign requires you to configure your own API key credentials. Once set up, Composio handles secure credential storage and API request handling for you.

### Can I use multiple toolkits together?

Yes! Composio's Tool Router enables agents to use multiple toolkits. [Learn more](https://docs.composio.dev/tool-router/overview).

### Is Composio secure?

Composio is SOC 2 and ISO 27001 compliant with all data encrypted in transit and at rest. [Learn more](https://trust.composio.dev).

### What if the API changes?

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)