Documentation
Verified people, and the applications they trust. These pages describe what the platform does today — nothing that is planned, and nothing that could not be read out of the running system.
Every page carries an availability badge and ends with what it does not do. The routes, scopes, checklist, webhook events and limits are read from the API's own export rather than typed, and every page names the API commit it was verified against.
Start at What UnifyID gives you, or go straight to your first verified sign-in.
Sections
- Get started
What the platform actually does, how to stand up a sandbox application, and what it takes to go live.
- Sign in
The OpenID Connect flow, the twenty-one claims you can ask for, and the honest limits of what comes back.
- Applications
Everything about an application after it exists: how you are signed in, how a live one changes, who is connected, who works on it, and who stands behind it.
- Platform
The hosts, the limits, the versioning promise, the public share links, and the words this documentation uses.
- Trust
What the platform seals, what it publishes for anyone to read, and exactly how much of it you can check without asking us.
- Reference
Every route the API serves to developers and to the public — 140 of them — read from the API source, not written by hand.
Verified against API commit 234dba22 on 2026-10-18. The routes, scopes, checklist, events and limits on these pages are read from that export, not typed.