Reference

This section is generated from the API at commit 234dba22, exported on 2026-10-18. It lists 140 routes: each one's method and path, who may call it, and the fields of the body it validates.

Routes behind the developer console session take the access token the developer console holds after you sign in to it with your UnifyID. There is no separate developer API key: see How you sign in.

Developer routes answer { "data": … }. OAuth and userinfo routes answer bare OpenID Connect payloads. Failures everywhere answer { "error": { code, message, requestId } } — see Errors and refusals.

Pages in this section

• Discovery and keys

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

• Sign in

  The authorization endpoint, the token endpoint, and the routes the hosted consent screen uses on the person's behalf.

• Userinfo

  What an access token can read: the flat claims map, the person's identity documents, and their profile picture.

• Applications

  Create, read, update, enable, disable and delete applications; environments, quickstart, activity, reach and the scope catalogue.

• Credentials

  Client secrets: issue, list, revoke, and remove the record of a revoked one.

• Production, releases and live changes

  The go-live checklist and review, the releases of a live application, and the live changes that apply at once.

• Test identities and testers

  Synthetic people a sandbox team signs in as, and the real people invited to try a sandbox application.

• Team, invitations and transfers

  Who works on an application, how they are invited, and how ownership moves.

• Publisher profiles

  The businesses or individuals a developer publishes under, the documents a reviewer reads, and submission for verification.

• Webhooks

  Endpoints, the event catalogue, test deliveries, secret rotation, delivery history and retries.

• Consents

  The consent register of an application: who is connected, with which scopes, since when.

• Alerts and support

  Which developer alerts reach you by email or in the console, and the support tickets raised from the console.

• Transparency and integrity

  The public checkpoint log, its keys, and the overview that reports both anchoring channels and the contract's governance.

• Other public routes

  Document share links, service status, maintenance notices, signed-out privacy requests, public support threads and documentation feedback.