Ignisign
Electronic signature platform for signature requests, signers, documents, webhook endpoints, and application authentication.
Tailored to esignature workflows that authenticate per environment, attach documents to signature requests, manage signers, and configure webhook endpoints.
Use Ignisign with Snow
Snow is a personal AI assistant that builds real apps for you, and they can put Ignisign to work.
What Snow can do with Ignisign
These are the Ignisign operations Snow and the apps you build with it can run. Sign in to choose which ones Snow may run without asking.
Reads14
Look at your data without changing it.
- Get application context
Tool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app.
- Get Document Information
Tool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID.
- 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.
- 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.
- 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.
- 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.
- 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)
- 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.
- 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.
- 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.
Creates4
Add something new to your account.
- 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 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.
- 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.
- 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.
Updates9
Change something that is already there.
- Create Signer
Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile.
- 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.
- Provide Document Content File
Tool to provide file content for a document. Use after creating a document to attach its file content.
- 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.
- Publish Signature Request
Tool to publish a draft signature request. Use after adding all documents and signer details to the draft.
- Update Document Information
Tool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation.
- Update Signature Request
Tool to partially update a signature request in DRAFT state. Use when you need to modify draft request metadata before sending.
- 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).
- 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`.
Deletes5
Remove something. This often cannot be undone.
- 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.
- Delete Document
Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete.
- 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.
- 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.
- 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.
Related integrations
Ready to put Ignisign to work?
Sign up free, build an app by chatting, and connect Ignisign in minutes. No credit card required.