Skip to main content
A workspace API key lets an app or script connect to Connie’s MCP server without signing in through a browser. Use one only when your app can’t sign in with OAuth. For Claude, ChatGPT, Claude Code, Cursor, VS Code and most other AI apps, sign in instead. Where: Settings → Developers → API keys · https://connie.ai/<workspace-id>/settings?tab=developers

​
Before you use a key

  • A key belongs to one workspace. It can’t switch workspaces. For several workspaces, create a key in each one or use OAuth.
  • A key acts as one member. It can do what that member can: the same role, records, lists and connected accounts. The row says Permissions of [member].
  • A key only works with the MCP server at https://mcp.connie.ai. The endpoints in the API reference use your browser session instead, so a key sent there returns 401. See Build on Connie.
  • Anyone with the key can act as you in that workspace. Keep it out of shared files, screenshots and chat histories.

​
Your personal key

The first time you open API keys, Connie creates a key for you named Personal key, with a Personal badge. It has Full access and acts with your permissions. You can use it straight away.

​
Create a key

1

Open API keys

Go to Settings → API keys (under Developers).
2

Generate a key

Click Generate API key. In the Generate API key dialog, enter a Name API key, named after the tool or computer that will use it (for example “Codex on laptop”; up to 100 characters).
3

Create and copy

Click Generate. A card shows New key: [name] with the key and a Copy button. Copy it. Keys start with sk_ followed by 64 letters and numbers.
The card also has Copy Codex setup prompt and Copy Cursor setup prompt. These copy a ready-made prompt to paste into those apps. The prompt includes your key, which then stays in that app’s chat history. Signing in with OAuth is safer; see Cursor and Other apps. You can copy a key you created again later: open its ⋯ menu and click Copy.

​
What each key row shows

  • The name, plus Personal for your auto-created key and Expired if it has expired.
  • The start of the key (sk_…).
  • Full access or Limited access.
  • “Created [date] by [member]” (keys made before keys had names show “Created before named keys”).
  • “Last used …” or “Never used”.
  • Permissions of [member], or Shared tools only if the key isn’t linked to a member. A Shared tools only key can’t read or change records, lists or tables.

​
Change which member a key acts as

Owners and admins only.
1

Open the key's menu

Click ⋯ on the key’s row and choose Permissions.
2

Pick a member

The Permission level dialog says the key “can do what the selected member can: the same role, records, lists and connected accounts.” Pick the member and click Save. You’ll see “Permission level saved”.
You can’t choose a member with a higher role than yours. For example, an admin can pick admins and members but not an owner. If you try, you’ll see “You can’t give a key a higher permission level than your own.”

​
Delete a key

Click ⋯ on the key’s row → Delete, then confirm Delete “[name]”?. “Anything using this key stops working immediately. Your other API keys are not affected.” There’s no rotate button. To rotate a key, generate a new one, switch your app to it, then delete the old one.

​
Use a key with an MCP app

Point the app at https://mcp.connie.ai and send this header:
For example, in Claude Code:
Or in an app’s JSON config that supports headers:
Send only one credential. Don’t send both an Authorization header and an X-API-Key header.

​
Good to know

  • Who can do what:
  • Limit: 50 active keys per workspace.
  • If the member a key acts as leaves the workspace, the key stops working.
  • Credits: actions made with a key use the workspace’s credits. They’re marked as made with an API key in Analytics → Tool activity and in the credit usage log. See Credits.
  • Watch the “Last used” date. Delete keys you no longer use.

​
Troubleshooting

Why: the key was cut off when copying. Keys start with sk_ followed by 64 letters and numbers. Fix: copy it again from Settings → API keys with the Copy button.
Why: the key was deleted, for example when its owner left the workspace. Fix: copy your current key, or generate a new one, and update the app’s settings.
Fix: copy your Personal key, or generate a new key, and update the app’s settings.
Fix: use the word Bearer, a space, then the key: Authorization: Bearer sk_....
Fix: keep only one header, ideally Authorization: Bearer <your key>, and remove X-API-Key.
Fix: use your own Personal key, or ask an owner or admin to change the key’s Permissions to a current member.
Why: it’s a Shared tools only key. Fix: use your Personal key, or ask an owner or admin to set the key’s Permissions.
Fix: use the other workspace’s own key, or connect with OAuth to reach all your workspaces.
Fix: close chats you aren’t using, or restart your app, then try again.
Fix: delete keys you no longer use, then generate the new one.
Fix: ask a workspace admin for member access. See Members and roles.
Why: those endpoints sign in with your browser session, not API keys. Fix: use the key with the MCP server at https://mcp.connie.ai, or send your session Cookie header to the API (see API authentication).