GET /v0/sis/pint/{id}/status — Returns 200 OK, proof that your verifier is wired up and ready to receive production traffic.
Prerequisites
- A dashboard account at dash.sis.sumvin.com.
- Credentials for an auth provider — either Dynamic or Privy. See the auth providers guide for where to find these in each console.
- A test environment you can use for local development.
Create your organisation
Sign in at dash.sis.sumvin.com and complete the onboarding wizard. Enter your organisation name and contact email. Your
organisation_id is auto-assigned and visible under Organisation → Settings — you will use it as a path parameter in SIS API calls.Create an environment
Go to the Environments page and click New environment. Give it a machine-readable name (for example
development) and a display label (for example Dev). Each environment gets its own environment_id and a separate set of SDK credentials — keep these scoped to the matching entry in your auth provider’s console.Configure an auth provider
Select your new environment, then open the Authentication tab. Choose Dynamic or Privy and paste the provider credentials for this environment. See the auth provider setup guide for where to find the right values.Once saved and activated, SIS validates JWTs issued by this provider for all requests scoped to this environment.
Add allowed origins
Open the CORS tab on any environment. Add the origins your app runs on — for example
http://localhost:3000 for local development or https://app.yourco.com for production.Mint an API key
Go to the API Keys page and click New API key. Give it a recognisable name and copy it when the dashboard shows it — the full key is displayed once, then only a prefix. Store it somewhere safe (a secret manager, not source control). See the API keys guide.
Run your first verifier call
Use the API key to hit the SIS revocation-status endpoint. This is the working artefact — a live, authenticated call against the SIS production API.You will see one of two responses, both of which confirm your key authenticated successfully:If the PINT URI exists: If it does not:
200 OK404 Not Found with an RFC 7807 error body. This is expected for the placeholder URI above — what matters is that SIS accepted your key and processed the request.Your verifier is wired up. Replace the placeholder URI with a real incoming PINT URI in production and you are ready to check revocations.
What’s next
| Next | Where | When |
|---|---|---|
| Standard verification | Verify a standard PINT | Five-minute end-to-end verifier quickstart |
| Verifier orientation | Verifier overview | What credentials you receive and what you need to verify |
| Core concepts | Organisations | The auth model — organisations, environments, and how they relate |
| Configuration depth | Auth providers | Providers, CORS origins, and API key management |