List Api Keys
Your API keys in this workspace (admins and owners: every member's), newest first, revoked ones included, with the grantable scopes. Signed-in users only: an API key gets 403 here.
API key access
/api/v1/workspaces/current/api-keysAccess token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).
In: header
Header Parameters
Id of the workspace to act on (must be a member).
Response Body
curl -X GET "http://localhost:8000/api/v1/workspaces/current/api-keys" \ -H "X-Workspace-Id: string"{
"items": [
{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"name": "Zapier sync",
"key_prefix": "ro_pat_Ab3dE",
"scopes": [
"string"
],
"user_id": "a169451c-8525-4352-b8ca-070dd449a1a5",
"user_email": "string",
"active": true,
"created_at": "2019-08-24T14:15:22Z",
"expires_at": "2019-08-24T14:15:22Z",
"last_used_at": "2019-08-24T14:15:22Z",
"revoked_at": "2019-08-24T14:15:22Z"
}
],
"available_scopes": [
{
"scope": "leads:read",
"description": "string",
"admin_only": true
}
]
}Create Api Key
Create a personal access token (`ro_pat_...`) for this workspace. It acts as you, capped by your current role and by its scopes; send it as `Authorization: Bearer <key>` (no `X-Workspace-Id` needed). The key is in the response only once. Granting `admin` needs the admin role; at most `API_KEY_MAX_PER_WORKSPACE` (default 50) active keys per workspace.
List Audit Log
The workspace's audit log, newest first: every state-changing request made with an API key (`via` = `api`), through the MCP server (`mcp`) or by a signed-in user (`ui`), with named actions for API keys, webhooks and privacy requests. Admins and owners (or a key with the `admin` scope). Entries are deleted after `AUDIT_LOG_RETENTION_DAYS` (default 90).