Lists API keys
GET/api/v1/api-keys
The key and its hash are never returned, only its prefix. New keys are created only in the dashboard: a key minting wider keys, or keys that survive its own revocation, would be a security hole. Needs admin permission. Scope: api_keys:read.
- Scope
api_keys:read- SDK method
- listApiKeys · list_api_keys
- MCP tool
listApiKeysread-only
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
limitquery | integer | no | Page size (1–200, default 50); 400 if it isn't an integerval 1–200, default 50 |
cursorquery | string | no | next_cursor from the previous response (opaque) |
Example request
curl -X GET "https://hiboty.com/api/v1/api-keys?limit=50" \
-H "Authorization: Bearer $HIBOTY_API_KEY"Example response (200)
{
"data": [
{
"id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"name": "Hiboty",
"prefix": "string",
"scopes": [
"string"
],
"access_level": "string",
"last_used_at": "2026-11-06T09:00:00.000Z",
"revoked_at": "2026-11-06T09:00:00.000Z",
"created_at": "2026-11-06T09:00:00.000Z"
}
],
"next_cursor": "string"
}Possible errors
400Invalid request: a missing or wrong field, or an unknown field name (validation_error).401The API key is missing, invalid or revoked (unauthorized).403Missing scope (scope), the plan doesn't allow it (plan_limit), the role isn't enough (forbidden_role), the email isn't verified (email_not_verified) or the organization is suspended.429A key, user or organization request limit (X-RateLimit-Scope) or the monthly message quota was exceeded; follow the Retry-After header.