CertSeal provides APIs for issuing and managing verifiable digital certificates, recipients, batches, designs, and webhook subscriptions.
Create a persistent certificate batch from an existing CertSeal design and optional email template. This consumes a batch slot and can fail when the plan batch limit is reached; designs and templates must already exist and are not created by this tool.
Create a persistent webhook subscription for selected certificate events. The response contains a wh_sec_ signing secret exactly once; capture it immediately and store it securely because later reads reveal only its tail. The workspace allows at most 20 subscriptions.
Permanently delete an issued recipient from an active batch. This cannot be undone, does not refund certificate quota, and permanently burns the certificate ID. Use only when permanent removal is intended.
Permanently delete a webhook subscription and stop future deliveries. This cannot be undone; create a new subscription to resume events.
Get one active or archived certificate batch by ID.
Look up an issued certificate using either its human-readable certificate ID or its public-viewer share token, and return its recipient, batch, design, and resolved variables. Provide exactly one lookup value.
Verify the connected CertSeal API key and return the workspace ID and username it belongs to. Use this to confirm account context before creating or changing resources.
Get one issued certificate recipient record by batch ID and recipient ID.
Get one webhook subscription by ID. This does not reveal the signing secret; it returns only the stored secret tail.
Atomically issue certificates for 1-100 recipients and queue email delivery for every created certificate. This irreversible external side effect requires every recipient to have an email address and the active batch to have an email template and configured mail delivery. Each recipient permanently consumes one certificate quota unit.
Atomically issue certificates without sending email for 1-100 recipients in one active batch. Each recipient permanently consumes one certificate quota unit even if later deleted; any invalid row, duplicate certificate ID, or quota failure creates none.
Return one newest-first page of certificate batches in the connected workspace, optionally filtered by archive state.
Return one newest-first page of reusable certificate designs. Designs are read-only through the API and must be authored in the CertSeal web app.
Return one page of issued certificate recipients in a batch, optionally filtered by email delivery status.
Return one newest-first page of webhook subscriptions. Stored signing secrets are never returned; secret_tail is only a non-sensitive identifier.
Immediately invalidate a webhook subscription's current signing secret and replace it. The new wh_sec_ secret is returned exactly once; capture and deploy it immediately or webhook verification will fail.
Sequentially queue real certificate emails for 1-25 existing recipients in one active batch. Each queued email is irreversible. Processing stops after the first failed or unknown attempt, and remaining recipients are marked not_attempted.
Queue asynchronous certificate email delivery to one recipient. This causes an external email side effect and requires a recipient email, a batch email template, and configured mail delivery; already queued or in-flight recipients and archived batches are rejected.
Idempotently archive or unarchive a batch. Archiving freezes recipient create, update, delete, and send operations but preserves existing certificate URLs; unarchiving re-enables those writes. This persistent change is reversible.
Enqueue one synthetic signed event through CertSeal's normal webhook dispatcher. This causes a real external delivery to the subscription URL; it does not only validate the subscription locally.
Partially update an issued certificate recipient. Only supplied fields change, while an explicit null clears an optional field; changing certificate_id must remain globally unique. Archived batches reject this mutation.
The CertSeal integration connects your Dench AI CRM directly to CertSeal, so agents can read and act on your CertSeal data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
21 actions are available for agents to invoke on your behalf. Every call runs through CertSeal's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find CertSeal and click Connect — you'll authorize access through CertSeal's own sign-in flow. No API keys or code required.
Ask an agent to use CertSeal in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench CertSeal integration connects your AI CRM to CertSeal, so AI agents can work with your CertSeal data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The CertSeal integration currently exposes 21 actions, including Create Batch, Create Webhook Subscription, Delete Recipient, Delete Webhook Subscription, Get Batch, and Get Certificate. Agents invoke them on your behalf from chat or from automations.
No. You connect CertSeal from your Dench workspace using CertSeal's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through CertSeal's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the CertSeal connection from your workspace settings at any time.