Call the API from your own backend
Queue a batch, check its status, and look up a finished certificate - the same pipeline the dashboard's bulk-generate wizard uses, with no separate rendering path.
See the endpointGenerate certificates, check batch status, and receive webhooks from your own backend. Available on the Business plan.
API keys
Create keyYour new API key
Copy it now. For your security, it will not be shown again.
cp_live_4f2a8d91e6b3c7a0f5d2b9c4e1a8f6d3Whichever fits your stack - direct API calls, a Zapier automation, or an AI assistant that already has access.
Queue a batch, check its status, and look up a finished certificate - the same pipeline the dashboard's bulk-generate wizard uses, with no separate rendering path.
See the endpointA published Zapier integration: a “New Batch Completed” trigger and a “Generate Certificate” action, so a batch finishing anywhere can kick off the rest of your workflow.
How triggers workA published MCP connector - no API key to copy, no terminal. Add it in Claude's Connectors settings and it signs in with your CertPie account directly.
See the connectorGenerate a key from Settings > API. It's shown in full exactly once - CertPie only ever stores its hash.
POST a template ID and a list of recipients. CertPie queues it for background generation and returns a batch ID right away.
Poll the batch by ID, or subscribe to the batch.completed webhook instead and skip polling entirely.
Once generated, fetch any certificate by ID for its PDF URL, its public verification link, and its status.
Subscribe to batch.completed and CertPie delivers a signed POST the moment a batch finishes - the same event that powers the Zapier "New Batch Completed" trigger. Every delivery follows the Standard Webhooks shape, so verifying one is a single HMAC-SHA256 check.
Webhook endpoints
Add endpointAdd webhook endpoint
CertPie sends a signed POST request here when a batch finishes.
Endpoint URL *
Must use https.