Skip to content

API keys

Call the DevBench API from your own scripts, with your account's access.

Where
API keysIn the app (sign-in required), opens in a new tab.
Reading time
1 min read
Who
Owner

How it works

A key lets a script call the DevBench API. It acts with your account's access, so it can use every endpoint you can, treat it as your password, not as a scoped token.

Send it as a Bearer token, or in an X-API-Key header, to any endpoint under /api.

Each workspace's box holds its own agent-scoped key, which is what devbench in that box authenticates with, that is why the keys list has a row named after each workspace. Revoking one stops that box's CLI, which is occasionally exactly what you want.

Steps

Following along? Tick each number off as you go.

  1. Open API keys from the organization's menu at the top left (or the search: Ctrl Ctrl, ⌘ ⌘ on a Mac). It opens as a tab where you are.

  2. Give the key a name and press Create key.

    The full value is shown once. Copy it now.

  3. Send it as Authorization: Bearer devbench_sk_… from your script.

    The page has a ready-made curl you can copy.

  4. Watch the last used column to find keys nobody needs any more.

  5. Press Revoke to switch one off, or Delete to remove the row entirely.

Worth knowing

  • A key is as powerful as your account. There is no narrower scope, so do not paste one anywhere you would not paste your password.

Read next

Running the organizationThe CLI, the desktop app and the phoneThe same account and the same workspaces from a terminal, a native window, or a phone in your pocket.Running the organizationTeam, roles and permissionsWho is in the organization, what each role reaches, who may spend money in the cloud, and how new people join.
Report a problem