Skip to main content
API keys give the management API and the MCP server access to one workspace. With a key, they can read and change automations, runs, tag mode, model access, and workspace secrets.

​
How keys work

  • A key acts as the member who created it. Changes made with it are recorded under that member’s name.
  • A key stops working when it is revoked or when its member leaves the workspace.
  • Superlog stores only a hash of the key. You can see the full key once, right after you create it.

​
Create a key

1

Open API keys

Go to Settings → API keys.
2

Name the key

Under Create an API key, enter a name that says where the key is used, such as Claude Code or CI, and click Create key.
3

Copy the key

Click Copy key and store it in your secret manager or MCP client. Keys start with slk_.

​
Revoke a key

Click Revoke next to the key. Anything that uses it stops working immediately. Members can revoke the keys they created. Admins and owners can revoke any key in the workspace. The API keys list shows the first characters of each key, the member it acts as, and when it was last used.