Skip to main content
GET /api/v1/projects/{project_id}/api-keys Requires api_keys.read permission. Plaintext key secrets are never returned in this listing — only metadata is returned.

Path parameters

project_id
string
required
UUID of the project.

Response

api_keys
APIKey[]
required
Array of API keys for the project.

Errors

StatusWhen
401Missing or invalid Bearer token
403Caller lacks api_keys.read permission

Example

curl http://localhost:8080/api/v1/projects/p1b2c3d4-e5f6-7890-abcd-ef1234567890/api-keys \
  -H "Authorization: Bearer <token>"
{
  "api_keys": [
    {
      "id": "k1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "project_id": "p1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "environment_id": "e1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "name": "Production Server Key",
      "scope": "server",
      "key_prefix": "tgl_srv_abc123",
      "last_used_at": "2026-03-20T08:00:00Z",
      "last_used_ip": "203.0.113.42",
      "expires_at": null,
      "revoked_at": null,
      "created_at": "2026-01-15T09:00:00Z",
      "updated_at": "2026-03-20T08:00:00Z"
    }
  ]
}

Build docs developers (and LLMs) love