Skip to main content
An API key lets your code act as this workspace. Manage it in Settings › API & MCP, under API key.

​
Before you start

  • Your role. Only owners and admins can make, replace or turn off a key. Other members can see its status.
  • Your plan. “API keys come with a paid plan (Software or Custom).” On Free, the card shows See plans and you can’t make a key. See Plans.
  • One key per workspace. Making a new one replaces the old one.

​
Make a key

1

Open the API key card

Go to Settings › API & MCP. It says “No key yet.”
2

Press Make a key

Your full key appears. It starts with b2b_sk_.
3

Press Copy and store it somewhere safe

We show it once and don’t keep a readable copy. Afterwards, the card shows only a masked version with the last 4 characters.
API key row with a masked key and its menu

After you make a key, the card shows who made it and only the last 4 characters.

Making a key costs nothing and sends nothing.

​
Use a key

Send it in the X-API-Key header:
Your base URL is in Developers overview.

​
What a key can do

There are no scopes. A key has owner-level access to its one workspace. It can’t reach any other workspace. Some actions always need a signed-in person, and some need Let AI tools approve and send messages turned on. See Permissions.
Treat your key like a password. Don’t put it in a shared document, a public repository or code that runs in a browser. Anyone who has it can act as your workspace.

​
Replace a key

Do this if a key may have leaked, or when someone who had it leaves.
1

Open the menu on the API key card

Press ⋯, then Make a new key….
2

Confirm

The current key stops working right away. Anything that uses it, like a Zapier step or your code, needs the new one.
3

Copy the new key and update your tools

This includes any MCP link, because the link carries the key.
You can’t undo this. The old key can’t be brought back.

​
Turn a key off

Press ⋯, then Turn off…. Anything that uses it stops working right away. You can make a new key any time. Turning a key off doesn’t stop your webhooks. They have their own signing secrets. To stop one, see Webhooks.

​
Troubleshooting

We can’t show it again. Make a new key, then update everything that used the old one.
The key is wrong or was replaced. Check that the whole key is in the X-API-Key header and that nobody made a new one.
If you’re a member, ask an owner or admin. If you’re an owner or admin, your workspace may be on Free, which has no API keys. See Plans.
A person must do that action while signed in. The detail field says so. See Permissions.

Developers overview

Base URL, permissions and limits.

MCP

Use your key with an AI tool.