Applications

Get started creates an application and takes it to production. This section is the rest of its life: the session that lets you manage it, the releases that change it once real people use it, the consents it holds, the testers and team around it, the publisher it goes out under.

Every route named here is in the Reference, generated from the API itself.

Pages in this section

• How you sign in

  There is no developer API key. Every developer route answers to the developer console's own session, which is an ordinary UnifyID sign-in.

• Changing a live application

  A sandbox application is edited in place. A live production application changes through releases, and production keeps serving until you switch.

• Consents

  The register of who is connected to your application, with which scopes, since when — metadata only, never claim values.

• TestersSandbox only

  Real people invited to try a sandbox application — the third way in, after the team and the test identities.

• Teams and ownership

  Five roles, invitations that last seven days, and ownership that moves only by a transfer the new owner confirms with a passkey.

• Publisher verification

  Who stands behind an application: a publisher profile, the documents a reviewer reads, and a verification status only staff can set.