Browse documentation

Design-partner preview

Getting started

The conceptual path from an operator-issued invitation to a reviewed application integration.

Before you begin

Developer registration is invitation-only. The invited owner completes the same SupahID verification, alias, password, and passkey pipeline used by the consumer product before returning to Console.

Conceptual integration path

  1. 01

    Redeem the invitation

    Validate the invitation in Console and complete or reuse a verified SupahID account.

  2. 02

    Describe the application

    Create the organization, initial application, test environment, exact redirects, and requested capability profile.

  3. 03

    Choose an identity mode

    Select hosted authentication or verified-human assurance based on what changes the application's decision.

  4. 04

    Implement the hosted flow

    Use Authorization Code with PKCE, exact redirect validation, state, and nonce once the sandbox publishes an executable contract.

  5. 05

    Prepare for live review

    Document claims, user disclosures, redirect ownership, policies, contacts, and the security controls required for production review.

What not to build yet

Do not infer endpoint paths, embed placeholder credentials, or ship a production dependency on the preview description. The sandbox contract will define the executable surface when it is authorized.