> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sumvin.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get a key from the developer dashboard

> Get an API key from the Sumvin developer dashboard, which is by invitation during the preview, and find your Organisation ID.

export const contacts = {
  verifierAccess: "hello@sumvin.com"
};

export const waitlists = {
  earlyAccess: "",
  payments: "",
  openBanking: "",
  developers: "",
  verifiers: ""
};

<Note>
  **Private preview:** this is rolling out and may not be available on your account yet.{waitlists.earlyAccess ? <> <a href={waitlists.earlyAccess}>Request early access →</a></> : null}
</Note>

A token an agent addresses to your website needs no key: you check it offline. A key is only for a service that already holds the signed request a person approved, for example for its own app. To [exchange that request](/sdk/verify/quickstart#services-that-already-hold-the-signed-request) and check it online, you need two things from the developer dashboard: an **API key** and your **Organisation ID**.

<Note>
  **Developer dashboard access is by invitation during the preview.** You can't sign up yourself yet.{waitlists.verifiers ? <> <a href={waitlists.verifiers}>Join the verifiers waitlist →</a></> : null}{contacts.verifierAccess ? <> For quicker access, email <a href={`mailto:${contacts.verifierAccess}`}>{contacts.verifierAccess}</a>.</> : null}{!waitlists.verifiers && !contacts.verifierAccess ? " A verifiers waitlist opens shortly." : null}
</Note>

<Steps>
  <Step title="Sign in to your organisation">
    Once you're invited, sign in at [dash.sis.sumvin.com](https://dash.sis.sumvin.com/sign-in). Your organisation has its own identifier.
  </Step>

  <Step title="Create an environment">
    Open **Environments** and create one, for example `development`. Every key belongs to an environment, so you need at least one.
  </Step>

  <Step title="Create a key">
    Open **API Keys** and select **Create key**. Choose **Standard SIS Key**, pick your environment, and name the key after where it will run, such as `local-dev`.

    Copy the key when it is shown. It is shown once; if you lose it, revoke it and create another.

    A Standard key can both exchange a Stamped Mandate for a token addressed to you and check it online. A **Public RPC Key** can do neither.
  </Step>

  <Step title="Copy your Organisation ID">
    Open **Organisation → Settings**. The **Organisation ID** there is the audience your tokens are addressed to. You pass it to every offline check of a token addressed to your organisation.
  </Step>
</Steps>

<Warning>
  Keep the key on your server. Anyone holding it can act as your organisation. Never put it in a browser, a mobile app or source control.
</Warning>

## Use the key

Send it as a bearer token:

```bash theme={null}
curl "https://sis.sumvin.com/v0/sis/pint/sr%3Aus%3Apint%3Atest/status" \
  -H "Authorization: Bearer $SUMVIN_API_KEY"
```

A `404` with code `PINT-404-001` here means the key works: no mandate with that identifier has a token addressed to your organisation. A `401` or `403` means the key or its permissions are wrong; see [Checks and errors](/sdk/verify/checks#errors).

## Next

<Card title="Verifier quickstart" icon="shield-check" href="/sdk/verify/quickstart">
  Check a Stamped Mandate, and exchange a signed request you already hold.
</Card>