Projects
—
Your workspaces
Vault / Overview
DEVELOPER WORKSPACE
Workspace overview
Welcome back.
A quick look at your projects, keys, and recent activity.
Total keys
—
Across all projects
Active keys
—
Currently enabled
API requests
—
This month
Your projects
Sign in to load your projects.
Recent activity
Your activity will appear here.
Developer API key
Keep this privateNot connectedYour key is used to identify your developer account. Never share it publicly.
Organize your work
Projects
Group scripts, keys, and settings by project.
All projects
0 projects| PROJECT | PROJECT ID | TYPE | KEYS | STATUS | CREATED |
|---|---|---|---|---|---|
| Connect your account to load projects. | |||||
Access management
Keys
Create, view, copy, and revoke access keys for your projects.
Create a project key
Only visible to your accountProject keys
0 keys| KEY NAME | KEY VALUE | PROJECT | STATUS | CREATED | ACTION |
|---|---|---|---|---|---|
| Sign in to load your project keys. | |||||
Keys are encrypted at rest. Anyone who obtains a key may be able to access the project it belongs to, so keep them private.
Public key page
Ad-gated accessChoose one provider for each project and add the offer link you created in that provider’s dashboard. Vault saves the public setup and gives you a shareable key-page URL.
Validate a project key
Integration endpointYour script can check whether a project key is active by sending the project ID and submitted key to Vault. A valid key returns {"valid":true}. An incorrect or revoked key returns {"valid":false}.
Setup tutorial
- Choose a project. Open the Projects section and create a project if you haven't made one yet.
- Copy the Project ID. Find it in the Project ID column of the Projects table. This ID identifies which project's keys Vault should check.
- Create a key. Open Keys → Create key, select that project, enter a name, and either let Vault generate a key or enter your own custom key. Copy the key value.
- Keep the key private. Put the key in a secure server-side configuration or secret store. Don't publish it in a public script or share it in screenshots.
- Send a validation request. From a trusted server-side script, send a POST request to the endpoint below with the project ID and key. Include the public Supabase
apikeyheader. - Check the response. Continue only when the JSON response contains
"valid": true. If it saysfalse, reject the key. Revoking a key makes future checks fail.
Request example
POST https://nqchpmrjcjrkjliydlhy.supabase.co/functions/v1/vault-dashboard
Content-Type: application/json
apikey: YOUR_SUPABASE_PUBLISHABLE_KEY
{
"action": "validate_project_key",
"projectId": "PASTE_PROJECT_ID_HERE",
"key": "PASTE_PROJECT_KEY_HERE"
}
Example response when valid
{"valid":true,"projectId":"YOUR_PROJECT_UUID"}
Important: run key validation from a trusted server-side script whenever possible. If you place a key in a client-visible script, users may be able to extract it. Never put a Supabase service-role key in a script.
Integrations
API access
Use your developer API key with supported Vault integrations.
Your API key
PrivateNot connectedYour API key is issued by the Vault backend and is unique to your account. Never put it in public frontend code or share it in screenshots.
Audit trail
Activity
A timeline of account and project events.
Recent events
Connect your account to load recent events.
Your account
Settings
Manage your profile and API credentials.
Account
Rotating creates a new key and immediately invalidates your previous key.