Docs
Dashboard

Start here

Quickstart

Create an application, generate an API key, and sign your first user up from your backend.

  1. 1

    Open a workspace

    Sign in to the dashboard and open My Workspaces. Pick a workspace you're a member of, or create one with New Workspace. Creating workspaces is invite-only for now.

  2. 2

    Create the application

    In the workspace open Applications and press Create App. Give it a name, your app's homepage URL (for example https://www.yourapp.com) and the type: Standard for a normal web or mobile app.

    Open the app and copy the Client ID under Client Credentials. This is your App ID; the API calls it appId.

  3. 3

    Register your callback URLs

    Only needed for Sign in with Google. Under Security URLs, add each address Identise may send users back to, one per line, for example https://www.yourapp.com/auth/identise/callback and http://localhost:3000/auth/identise/callback for development. See the rules.

  4. 4

    Generate an API key

    Under API Keys press Generate Key and copy it straight away: it's shown only once. Store it in your backend's secret store, for example as IDENTISE_API_KEY. Never put it in a browser bundle or a mobile app.

  5. 5

    Sign a user up from your backend

    Every call your backend makes sends the key in X-Api-Key:

    bash
    curl -X POST https://api.identise.com/v1/oauth/register \
  -H "Content-Type: application/json" \
  -H "X-Api-Key: $IDENTISE_API_KEY" \
  -d '{"appId":"<your Client ID>","email":"ada@example.com","password":"correct horse battery staple"}'

    The answer holds an accessToken (15 minutes by default) and a refreshToken (30 days by default). Keep both on your server, or the refresh token in an HttpOnly cookie.

  6. 6

    Check the token on every request

    Your services verify access tokens themselves, offline, with your app's public keys: see Verifying access tokens.

Replace https://api.identise.com with the address of your Identise deployment. Every route is under /v1.

Next steps