Skip to content

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.

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
  1. Open Settings → API keys and press Create key.
  2. Enter a Name that says what uses it, for example github-actions.
  3. Choose Access, Reaches and Ends after.
  4. 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.

Send it in the Authorization header:

Terminal window
curl -H "Authorization: Bearer wsla_key_..." \
https://dashboard.sbx09.online/api/orgs

The 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.

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.