Authentication
One API key per integration, sent as a bearer token. Keys act for one workspace.
Create a key
- In Fifty Eight, open API & MCP in the sidebar. You need to be an owner or admin of the workspace.
- Name the key after where it will be used (“Claude Code”, “n8n”…).
- Copy the key. It starts with
fe_live_and is shown only once: Fifty Eight stores a hash, not the key.
Send it
Put the key in the Authorization header of every request:
curl https://api.72-62-237-85.sslip.io/v1/accounts \
-H "Authorization: Bearer $FIFTYEIGHT_API_KEY"The CLI reads it from fiftyeight auth login or the FIFTYEIGHT_API_KEY environment variable. MCP clients send the same header (see MCP server).
What a key can do
- A key acts with admin rights inside its workspace: it can connect accounts, publish, dub and use the workspace's credits.
- A key can only use credits, never spend money: buying credits, plans, automatic top-up, extra accounts and invoices are done by a signed-in owner or admin on the dashboard's Plan & credits page. Those calls answer
403to a key. - It cannot manage members, workspaces or other API keys. Those endpoints only accept a signed-in user in the app.
- It never sees another workspace. Ids from another workspace answer 404.
Revoke a key
In API & MCP, each key shows when it was last used. Revoke it there: requests with it answer 401 Invalid API key right away.
Treat a key like a password: keep it in an environment variable or a secret manager, never in a repository or a client-side app. If one leaks, revoke it and create a new one.
Errors
401 Missing bearer token: noAuthorization: Bearer …header.401 Invalid API key: unknown or revoked key.403: the action needs more than a key allows, or more than your plan includes.