Supah developer documentation

Understand the intended integration model, identity boundaries, and review path before executable application identity endpoints become available.

Start with the model

Supah gives applications two ways to use hosted, consent-bounded identity. The documentation describes those modes without presenting planned endpoints as operational.

GuideGetting started

The conceptual path from invitation to reviewed integration.

GuideIntegration modes

Choose Continue with Supah or Verify with Supah.

GuideIdentity model

Pairwise subjects, claims, scopes, consent, and assurance.

GuideEnvironments and access

How test and live access remain separate and reviewed.

GuideSecurity checklist

Implementation requirements and data-minimization boundaries.

What is available today

Invited design partners can enter the Console onboarding path and describe an application. Source-level management contracts and test harnesses do not make public identity APIs or credentials operational.

Executable quickstarts, discovery, test identities, SDKs, and API reference will ship only with an authorized sandbox and a public application identity contract.

Where the consumer experience lives

SupahID remains the hosted human-facing verification, sign-in, and consent experience. Developers configure an integration through Supah Developer; people complete the human flow through SupahID.

Understand SupahID for applications ↗