API keys
Create, store, and revoke Silos API keys for the CLI, SDKs, and REST API.
API keys authenticate management calls — creating databases and branches, reading usage, and everything the CLI, SDKs, and REST API do on your behalf. You create and revoke them in the Console.
An API key grants access to your account's management surface. Treat it like a password: store it in a secret manager or environment variable, never commit it to source control, and revoke it immediately if it leaks.
Create a key
Open API keys
In the Console, go to API keys in your account or project settings.
Create a new key
Click New key, give it a descriptive name (for example, ci-pipeline or
local-dev), and create it.
Copy it now
The key's secret is shown once, at creation time. Copy it and store it somewhere safe — you won't be able to view it again.
You can also create keys from the CLI with silos auth keys.
Use a key
Provide the key to the CLI, an SDK, or a raw API call. The common pattern is an environment variable:
export SILOS_API_KEY="sk_..."The CLI and SDKs read SILOS_API_KEY automatically. For raw API calls, pass it as a
bearer token:
curl "https://api.silos.sh/v1/projects" \
-H "Authorization: Bearer $SILOS_API_KEY"API keys are for the management API. Connecting to a database to run SQL uses the database's connection string over TLS, not an API key.
Revoke a key
From the API keys page, revoke any key you no longer need or that may have been exposed. Revocation takes effect immediately — calls using that key stop working. Rotate keys periodically and after any team change.