Connect CertSeal to your AI agent
CertSeal provides APIs for issuing and managing verifiable digital certificates, recipients, batches, designs, and webhook subscriptions.
We set up the connection using your own CertSeal account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.
Actions
What your agent can do in CertSeal
Each one is a real action the agent can take on its own, the same things a person clicking around CertSeal could do. Read-only by default; write actions are confirmed against your policy.
- Create Batch 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…
- Create Webhook Subscription 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 tai…
- Delete Recipient 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.
- Delete Webhook Subscription Permanently delete a webhook subscription and stop future deliveries. This cannot be undone; create a new subscription to resume events.
- Get Batch Get one active or archived certificate batch by ID.
- Get Certificate 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.
- Get Current Workspace 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 Recipient Get one issued certificate recipient record by batch ID and recipient ID.
- Get Webhook Subscription Get one webhook subscription by ID. This does not reveal the signing secret; it returns only the stored secret tail.
- Issue and Send Certificates 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…
- Issue Certificates 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…
- List Batches Return one newest-first page of certificate batches in the connected workspace, optionally filtered by archive state.
- List Designs 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.
- List Recipients Return one page of issued certificate recipients in a batch, optionally filtered by email delivery status.
- List Webhook Subscriptions Return one newest-first page of webhook subscriptions. Stored signing secrets are never returned; secret_tail is only a non-sensitive identifier.
- Rotate Webhook Signing Secret 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.
- Send Certificate Emails 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 ma…
- Send Recipient Certificate Email 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…
- Set Batch Archived State 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…
- Test Webhook Subscription 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.
- Update Recipient 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.
Setup
How we connect it
- 1
Connect your account
You create a key in CertSeal, a key you create and control, and paste it in once. It lives in a secrets store on your server, not with us.
- 2
Set the guardrails
Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.
- 3
We keep it running
Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.
FAQ
CertSeal questions, answered.
With a key you create and control. You paste it in once, it is stored in a secrets store on your server, permissions are scoped to the minimum the agent needs, and you can revoke it at any time.
The actions CertSeal's API allows, the same things a person clicking around the app could do. Connections start read-only by default; write actions are confirmed against the policy you set before the agent takes them.
Connections are priced per tool on top of the base plan. Some are included, some are premium. See pricing for how connection charges work.
Standard tools are ready inside 7 business days of the setup call. We test the connection end to end, walk you through how the agent uses it, and watch the first week of activity.
Ready to put CertSeal to work?
Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.
All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by CertSeal.