AI agent integrationIgnisign

Ignisign integration for multiplayer collaboration with AI agents using Claude Code or Codex

One governed connection your whole team and its AI agents can share, with approved actions and human review, so working in Ignisign never means pasting credentials into a prompt.

Request access See API details

CategoryDocuments & Forms

Use Ignisign from Claude Code

Bring Ignisign context into engineering work while Type keeps app access attached to the teammate and workspace.

Automate Ignisign with Codex

Let coding agents ask for the right app action, preserve conversation context, and keep humans in the approval loop.

Connect open agent workflows

Use Type as the collaboration layer around OpenClaw and other LLM workflows that need app access.

Documents & Forms

What the Ignisign integration exposes

IgniSign is a comprehensive electronic signature platform that enables users to sign, send, and manage documents securely online.

One connection, many teammates

Connect Ignisign once, then decide which teammates can use it for threads, automations, skills, and coding work.

Representative actions

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.
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.
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.
Create Signer
Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile.
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.

Connection

API and auth details

IgniSign documents an electronic-signature API with bearer API keys and signature-process tokens. Integrations can create signature requests, manage documents, signers, signer profiles, proofs, seals, bare signatures, log capsules, user invitations, webhooks, and embedded signing workflows.

Source: Type catalog metadata
Auth schemes: API key
API docs: https://ignisign.io/docs/category/ignisign-api
API reference: https://ignisign.io/docs/ignisign-api/ignisigns-api
Auth docs: https://ignisign.io/docs/ignisign-api/ignisigns-api#authentication
Official site: https://ignisign.io/

Source links

FAQ

Questions people ask before connecting Ignisign

Can Claude Code use Ignisign?

Yes. Type lets an AI teammate use connected Ignisign actions from a governed workspace context, so Claude Code work can reference the app without copying credentials into a local prompt.

Can Codex work with Ignisign through Type?

Yes. Codex can collaborate through Type with app context, skills, and approved actions. The Ignisign catalog entry includes public integration details and example capabilities where available.

Is this the same as a Ignisign MCP server?

Type exposes connected app capabilities to AI teammates and coding agents through Type's integration layer. Teams use it when they want shared app access, human review, and teammate-level permissions around agent work.