Userinfo
What an access token can read: the flat claims map, the person's identity documents, and their profile picture.
5 routes
Every route here takes the access token from the token endpoint as a bearer token. Each answer is recorded as a disclosure to your application in the transaction that reads the data.
The guide for this family is Handling the callback.
POST /v1/profile-photo-comparisons
POST /v1/profile-photo-comparisonsAuthentication- OAuth access token (bearer)
GET /v1/userinfo
GET /v1/userinfoAuthentication- OAuth access token (bearer)
GET /v1/userinfo/identity-documents
GET /v1/userinfo/identity-documentsAuthentication- OAuth access token (bearer)
GET /v1/userinfo/identity-documents/{documentReference}
GET /v1/userinfo/identity-documents/{documentReference}Authentication- OAuth access token (bearer)
GET /v1/userinfo/picture
GET /v1/userinfo/pictureAuthentication- OAuth access token (bearer)
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.