Supabase secret key
ID supabase_secret_key
DatatypeNot PIIidentifierDraft
This record is a draft: it has not been reviewed yet and may be incomplete or wrong. Do not rely on it for compliance decisions. Help improve it (see CONTRIBUTING.md).
Secret API key of a Supabase project, which bypasses row level security and must stay on the server. Supabase documents that secret keys start with sb_secret_ and are short strings, not JWTs; the legacy service_role key is a JWT and is the datatype jwt. The vendor does not document the length or the characters after the prefix; the regexp accepts letters and digits.
- Parent datatype
- API key or client secret
api_key - Categories
- Secrets and credentials (passwords, keys, tokens)
- Countries
- Global (not tied to a country)
- Languages
- Common to most languages
- Quality
- 70/100 · missing: examples, mapping (Wikidata, Schema.org, ...), translation
- Metacrafter rules
- no detection rule yet
- Supported by tools
- Datadog Sensitive Data Scanner, GitHub secret scanning
Regular expression
^sb_secret_[A-Za-z0-9_-]+$
Python re syntax.
Examples
| Value | Description |
|---|---|
| sb_secret_ invalid | Prefix without the secret |
Sources
Use this record
- Page URL:
https://registry.apicrafter.io/datatype/supabase_secret_key - JSON: API v1 · legacy shape (used by metacrafter) · Markdown (for LLMs)
- Improve it: edit
data/datatypes/any/secrets/supabase_secret_key.yamlon GitHub