list_signers
List Signers
Retrieve a paginated list of signers, optionally filtered by a search query. Use this to browse or search for existing signers in your application.
list_signers
Retrieve a paginated list of signers, optionally filtered by a search query. Use this to browse or search for existing signers in your application.
get_signature_request
Retrieve the full context of a signature request including its status, associated documents, signers, and configuration.
get_signer
Retrieve details of a specific signer including their profile, claims, and status.
create_signature_request
Initialize a new signature request, optionally configure it with documents, signers, and metadata, then publish it for signing. Supports the full lifecycle: init → update → publish in a single call, or just initialization for later configuration.
manage_signature_request
Update, publish, or close an existing signature request. Use this to modify a draft request's configuration, launch it for signing, or close a completed/cancelled request.
create_signer
Create a new signer for use in signature requests. The required inputs depend on the signer profile — use the "List Signer Profiles" tool first to determine which fields are needed.
list_signature_requests
Retrieve a paginated list of signature requests for the configured application and environment.
get_application_context
Retrieve the complete application context including configuration, settings, available signature profiles, signer profiles, and environment details. Useful for understanding the application setup.
list_signer_profiles
Retrieve available signer profiles and their required inputs. Signer profiles define what identity information is needed to create a signer. Use this to understand what inputs are required before creating signers.
update_signer
Update an existing signer's inputs (claims) such as name, email, phone number, or other identity attributes. Can also be used to revoke a signer.
list_signature_profiles
Retrieve available signature profiles for the configured application and environment. Signature profiles define the signature mechanism, document types allowed, legally binding value, and integration mode (By-Side or Embedded).
upload_document_content
Upload content to a previously initialized document. Supports file content (base64-encoded for PDF/images) or structured JSON data.
manage_document
Initialize, retrieve, update, or delete documents within signature requests. Documents must be initialized before content can be uploaded. Supports PDF, DOCX, images, and structured data.
seal_document
Apply a corporate electronic seal (E-Seal) to documents using a machine-to-machine (M2M) emitter. E-Seals prove the origin and integrity of corporate documents without requiring individual signers.
get_signature_proof
Retrieve signature proof artifacts for a signed document, including signature images (base64) and low-level cryptographic proofs. Use this after a document has been signed to get proof evidence.
Create, manage, and verify legally binding electronic and digital signatures on documents. Upload PDFs, DOCX, images, and raw data for signing. Configure signature profiles with multiple signature levels (Simple, Advanced, Qualified) compliant with eIDAS, ESIGN, and UETA regulations. Create and launch signature requests, manage signers and their required identity inputs, and track signature progress through real-time webhooks. Retrieve signature proofs including XAdES files, ASiC-E containers, proof PDFs, and signature images. Automate corporate electronic seals for machine-to-machine document sealing. Embed signature sessions into applications or use Ignisign-managed email-based signing flows. Manage webhook endpoints to receive notifications for signer, signature request, proof, and document events.
Common questions about connecting Ignisign to AI agents with Metorial.