Documentation

Watching credentials you rely on

A verifier account, a watchlist, and a webhook the moment something changes.

If you checked a credential last March and relied on it, you have a problem the check page cannot solve: it was valid in March, and you have no idea whether it still is.

A verifier account is for that. Register, confirm your email, take a key:

POST /api/verifier/register   { "name": "Example Checks", "email": "[email protected]" }
POST /api/verifier/verify-email  { "verifierId": "...", "code": "123456" }
POST /api/verifier/keys          { "verifierId": "...", "code": "123456", "name": "Production" }

Watch a cohort

POST /api/verifier/watchlist
Authorization: Bearer <verifier key>

{ "items": [{ "code": "ACME-MERN-NOV26-0007", "cohort": "nov-2026" }] }

An ID that currently matches nothing is accepted rather than refused — a candidate often hands over an ID before the issuer has published it — and the response tells you which of yours resolved.

Be told

Register an endpoint and you are notified the moment a watched credential is revoked, suspended, unsuspended, expires, or has its expiry changed. In the same request as the change, not on a later sweep, because minutes between a revocation and the people relying on it is the whole thing you are here for.

Your own trail

Every check made with your key is recorded: what you asked, when, and what you were told — including "it does not exist", which is the half of the trail easiest to forget to keep and most often the one that matters.

What an account does not buy

Checking. A single credential, and batches of 25, are free and account-free forever. An account buys watching.