CERTINATOR / PRODUCT

Certificate PDF automation with the API and MCP

Connect certificate generation to an existing application or an authorized automation.

Fictional product example · no real messages or public records

GET /api/v1/templates
Authorization: Bearer YOUR_SERVER_SIDE_API_KEY

POST /api/v1/render
Content-Type: application/json

See Developers for the current request schema.

How it works

Choose a plan with API access and create an appropriately scoped key in Settings.
Use the endpoint examples and current schema on the Developers page.
Generate a small request or submit a background job, then inspect the response and download result.
Treat public issuance and revocation as separate, deliberate actions. Keep keys on the server.

Limits and prerequisites

API/MCP use API credits, not web-editor allowance. Direct requests support up to 10 PDFs; background jobs up to 100. Daily credits, request rate, and concurrency limits also apply. Do not send keys or recipient contents to analytics.

Open API and MCP documentation →

Continue learning

Generate certificate PDFs through the API · Current plans and allowances · Explore the fictional sample journey