---
title: "List API key metadata"
method: GET
path: "/v1/keys"
tags: ["Key Management"]
---

# List API key metadata

`GET /v1/keys`

## Request

- Base URL: `https://api.nashboard.ai`
- URL: `https://api.nashboard.ai/v1/keys`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Required scope: `keys:read`. Returns metadata only — never the hash or plaintext (unrecoverable by design).

## Headers

- `X-Nashboard-Version` '2026-06-13'

## Response `200`

List of key metadata objects.

- object
  - `data` KeyMeta[], required
    - `id` string, uuid, required
    - `prefix` string, required
    - `name` string, nullable
    - `scopes` string[], required
    - `last_used_at` string, date-time, nullable
    - `expires_at` string, date-time, nullable
    - `created_at` string, date-time, required

## Other responses

- `400`: Bad request (invalid JSON, invalid ID, invalid cursor, etc.)
- `401`: Missing, malformed, or invalid API key.
- `403`: Insufficient scope or scope escalation attempt.
- `404`: Resource not found.
- `409`: Conflict (e.g. email already taken).
- `413`: Request body too large.
- `415`: Unsupported media type.
- `422`: Request body failed schema validation.
- `429`: Rate limited, quota exceeded, or DP budget exhausted.
- `500`: Internal server error.
- `502`: Upstream dependency error (e.g. receipt image storage unavailable — code storage_failure).

---

[API](https://skmtc.dev/nashboard/apis/nashboard-b2b-api.md) · [All operations](https://skmtc.dev/nashboard/apis/nashboard-b2b-api/llms.txt) · [OpenAPI document](https://skmtc.dev/nashboard/apis/nashboard-b2b-api/revisions/a51f5ab22ec5?raw)
