SuperTokens

Record your SuperTokens connection as identity & sso evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In SuperTokens:

   1. Self-hosted SuperTokens Core: choose an API key value and set it in the Core configuration, either as the api_keys setting in config.yaml or as the API_KEYS environment variable for the Docker image.
   2. Restart the Core so the key takes effect, then paste the same value into Safeguard.

   Where to find the other values:

   • Base URL (optional): The connection URI of your SuperTokens Core (the address your backend SDK uses to reach the Core).

   SuperTokens's public documentation does not cover every step.

   SuperTokens' API-keys page states it is only relevant when self-hosting; the key is a value you define in config, not one issued by a UI, and the Core can administer users and sessions (no read-only scope is documented). After changing keys, deploy or restart every Core instance. Where managed-service (SaaS) users find their connection URI and API key was not found in the docs read.

   Source: supertokens.com, supertokens.com, checked 2026-10-07.

2. On Compliance › Connectors, open SuperTokens, click Connect, choose API token and fill in:

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

No automated compliance test reads SuperTokens yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

Related

• Identity & SSO connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks