Discovery and keys

The well-known documents: OpenID Connect discovery, the token-signing JWKS and the checkpoint signing keys.

3 routes

Read these rather than hard-coding anything from this site. None of them takes a credential.

The guide for this family is How the flow works.

GET /.well-known/jwks.json

GET /.well-known/jwks.json

Authentication: None

GET /.well-known/openid-configuration

GET /.well-known/openid-configuration

Authentication: None

GET /.well-known/unifyid-checkpoint-keys.json

GET /.well-known/unifyid-checkpoint-keys.json

Authentication: None

What this does not do

Responses are not listed. The API declares no response types, so this page describes what to send and who may send it. Recorded response shapes are on the guides.
This page is generated. It was read from the API at commit 234dba22. Editing it by hand changes nothing; the next sync overwrites it.

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.