API keys
An API key lets a program work with the platform: a script, a CI job, or an agent that cannot sign in through OAuth. Only owners and admins see Settings → API keys.
What a key can do
Section titled “What a key can do”A key acts as the person who made it, in this organization only, with that person’s role, capped by the key’s own access:
| Setting | Choices |
|---|---|
| Access | Read-only: look, never change. Full: also deploy, back up and change, within your role |
| Reaches | The whole organization, or one project: its environments, their backups and tasks, nothing else |
| Ends after | A period after which the key stops working, or Never |
Create a key
Section titled “Create a key”- Open Settings → API keys and press Create key.
- Enter a Name that says what uses it, for example
github-actions. - Choose Access, Reaches and Ends after.
- Create it and copy the key. It starts with
wsla_key_and is shown once.
Keep it like a password: in your CI system’s secrets, never in a repository.
Use a key
Section titled “Use a key”Send it in the Authorization header:
curl -H "Authorization: Bearer wsla_key_..." \ https://dashboard.sbx09.online/api/orgsThe same key works on the REST API (REST API basics) and on the MCP endpoint https://dashboard.sbx09.online/mcp for agents that take a token instead of signing in.
Revoke a key
Section titled “Revoke a key”On Settings → API keys, use revoke on the key’s row and confirm with Revoke key. It stops working at once.
The list shows each key’s name, the first characters of the key and when it was last used, never the key itself.

