otherapi_key

CertSeal

CertSeal provides APIs for issuing and managing verifiable digital certificates, recipients, batches, designs, and webhook subscriptions.

Integration

Vendor
CertSeal
Category
other
Auth
API_KEY
Tools
21
Composio slug
cert_seal

Tools

  • 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 and are not created b

  • 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 tail. The workspace allo

  • Delete Recipient
    destructive

    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
    destructive

    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 have an email templa

  • 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 ID, or quota failure

  • 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 marked not_attempted.

  • 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 recipients and archi

  • 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 reversible.

  • 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

  1. Create or open a Switchy Project.
  2. Open Integrations and connect CertSeal.
  3. Authorise through api_key. Switchy stores the connection against your org.
  4. Everyone in the Project can now @-mention the CertSeal tools in chat.

What teammates see: by default, memories from CertSeal are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Projects have used this MCP together with a given model.

How Switchy teams use it

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

Starter prompts for this model will land here soon.

More other MCPs

See all other MCPs

Data last verified 7 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.