Skip to main content
Private preview: this is rolling out and may not be available on your account yet.
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 and check it online, you need two things from the developer dashboard: an API key and your Organisation ID.
Developer dashboard access is by invitation during the preview. You can’t sign up yourself yet.
1

Sign in to your organisation

Once you’re invited, sign in at dash.sis.sumvin.com. Your organisation has its own identifier.
2

Create an environment

Open Environments and create one, for example development. Every key belongs to an environment, so you need at least one.
3

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.
4

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.
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.

​
Use the key

Send it as a bearer token:
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.

​
Next

Verifier quickstart

Check a Stamped Mandate, and exchange a signed request you already hold.