Use case
Certificates people can actually verify.
Mark a certificate template for verification and every render gets a public verify page plus an optional trackable QR code — so a recipient (or anyone checking their claim) can confirm it's genuine without contacting you.
How it works
- 1Design a certificate template and mark it data-verify="true". Optionally add a QR code field marked data-qr-tracked.
- 2Render one certificate per recipient — in bulk if you're issuing many at once for a course or event.
- 3Each render gets its own public, permanent verify URL. Anyone who scans the QR code or visits the link sees the exact data the certificate was issued with.
Before & after
Anyone can claim a certificate is real — there's no way to check.
A data-verify="true" template gives every render a public, permanent verify page with the exact data it was issued with.
A printed certificate has no way to be checked from a phone.
An optional tracked QR code resolves straight to that verify page — scan it, see the result.
Issuing 500 certificates for a course cohort one at a time.
Bulk rendering issues the whole batch in one API call, one certificate per recipient.
Faking or editing a certificate after the fact.
The verify page snapshots the data at render time — what it shows can't drift from what was actually issued.
Who it's for
Course platforms
Issue a verifiable completion certificate the moment a learner finishes, with a QR employers can scan.
Event organizers
Bulk-generate attendance or participation certificates for an entire event roster in one call.
Certification bodies
Give every credential a permanent, public verify link that stands up to scrutiny.
Frequently asked
How does someone actually verify a certificate?
Every render of a data-verify="true" template gets its own public verify URL. Visiting it (or scanning the certificate's QR code) shows the exact data the certificate was issued with — name, date, whatever fields you included.
Do I need a QR code, or does verification work without one?
The verify page exists regardless. A tracked QR code (data-qr-tracked) is optional — it just makes the verify page reachable by scan instead of typing a URL, and gives you scan analytics.
Can I issue certificates for a whole cohort at once?
Yes. Send an array of recipient records to the bulk endpoint and get back one certificate per record, each with its own verify page, in a single call.
Does anyone need an API key to verify a certificate?
No. Verification lookups are public and unauthenticated — an API key is only needed to create renders, not to check one.
Auto-generate certificates from Google Sheets for a course or LMS
Feed a roster — a Google Sheet, an LMS export, an array of recipients — to the bulk endpoint and get back one certificate per learner, each with its own public verify URL and optional tracked QR code. It fits course platforms and certification bodies that issue credentials employers need to authenticate from a phone.