API keys API

Organization keys for your backend, the CLI, MCP and CI. 3 ops: list_api_keys, create_api_key, revoke_api_key.

Organization keys for your backend, the CLI, MCP and CI.

List API keys · POST /api/v1/list_api_keys · scope keys:read or GET …?input=

API keys of this organization (prefix only; the full key is shown once at creation), each with the role it acts with, its scopes and who created it. Owners and admins see every key; members see their own. Also returns available_scopes.

curl -X POST https://getwabi.dev/api/v1/list_api_keys \  -H "Authorization: Bearer wabi_…"

Create API key · POST /api/v1/create_api_key · scope keys:write

Create an organization API key for your backend, the CLI, an MCP host or CI. It acts with your role (an owner's key acts as admin), optionally narrowed to scopes, and keeps working if you leave the organization; admins can revoke it. The full key (wabi_…) is returned only once; store it as a secret and never ship it to a browser or app.

curl -X POST https://getwabi.dev/api/v1/create_api_key \  -H "Authorization: Bearer wabi_…" \  -H "Content-Type: application/json" \  -d '{"name":"Support"}'

Revoke API key · POST /api/v1/revoke_api_key · scope keys:write

Revoke an API key immediately; every backend, CLI, CI job or MCP host using it stops working. Owners and admins revoke any key; members their own.

curl -X POST https://getwabi.dev/api/v1/revoke_api_key \  -H "Authorization: Bearer wabi_…" \  -H "Content-Type: application/json" \  -d '{"key":"6f1c2e0a-4b7d-4c2e-9a51-0d3b8e7f9a10"}'