CertSeal for AI agents
Agents read CertSeal at once. Changes and sends are held for a person's approval by default.
About CertSeal
CertSeal provides APIs for issuing and managing verifiable digital certificates, recipients, batches, designs, and webhook subscriptions.
What an agent can do in CertSeal
Every CertSeal action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in CertSeal without asking first. 9 actions.
- Get BatchGet one active or archived certificate batch by ID.
- Get CertificateLook 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 look
- Get Current WorkspaceVerify 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 RecipientGet one issued certificate recipient record by batch ID and recipient ID.
- Get Webhook SubscriptionGet one webhook subscription by ID. This does not reveal the signing secret; it returns only the stored secret tail.
- List BatchesReturn one newest-first page of certificate batches in the connected workspace, optionally filtered by archive state.
- List DesignsReturn one newest-first page of reusable certificate designs. Designs are read-only through the API and must be authored in the CertSeal web app.
- List RecipientsReturn one page of issued certificate recipients in a batch, optionally filtered by email delivery status.
- List Webhook SubscriptionsReturn one newest-first page of webhook subscriptions. Stored signing secrets are never returned; secret_tail is only a non-sensitive identifier.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 12 actions.
- Create BatchCreate 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
- Create Webhook SubscriptionCreate 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
- Delete RecipientPermanently 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 inte
- Delete Webhook SubscriptionPermanently delete a webhook subscription and stop future deliveries. This cannot be undone; create a new subscription to resume events.
- Issue and Send CertificatesAtomically 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
- Issue CertificatesAtomically 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, dup
- Rotate Webhook Signing SecretImmediately 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 f
- Send Certificate EmailsSequentially 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 remainin
- Send Recipient Certificate EmailQueue 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
- Set Batch Archived StateIdempotently 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 pe
- Test Webhook SubscriptionEnqueue 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.
- Update RecipientPartially 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 re
Changes wait in Needs you
Changes and sends in CertSeal are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
CertSeal questions
Can an agent change data in CertSeal on its own?
Not by default. Changes and sends in CertSeal are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in CertSeal?
This connector lists 9 read actions. Reads run at once, without waiting for approval.
How does CertSeal connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.