---
title: "List API keys"
method: GET
path: "/api-keys"
---

# List API keys

`GET /api-keys`

## Request

- Base URL: `https://app.yoping.me/api/v1`
- URL: `https://app.yoping.me/api/v1/api-keys`
- Auth: API key in cookie `yp_session`

Lists the account's MCP API keys (revoked ones included). Key management requires a browser session; an API-key-authenticated caller gets 403.

## Response `200`

The account's API keys.

- object: Uniform success envelope: the payload is always under `data`.
  - `data` ApiKey[], required
    - `id` string, required
    - `name` string, required
    - `prefix` string, required: First 12 characters of the raw key ("ypk_" plus 8), for display.
    - `scopes` string[], required: Scopes the key carries. Always includes 'mcp'; 'mcp:write' additionally admits it to the MCP write tools.
    - `created_at` string, date-time, required
    - `last_used_at` string, date-time, nullable, required
    - `revoked_at` string, date-time, nullable, required

## Other responses

- `401`: Not authenticated (code `unauthorized`): missing, invalid, or expired session; invalid login credentials; or a Bearer token, which this surface rejects.
- `403`: Forbidden. Code `forbidden` for a cross-origin (CSRF) request blocked by origin validation or for API-key management attempted without a browser session; `account_suspended` when a suspended account attempts a mutation; `account_deleted` when an account in its deletion grace window calls a non-exempt route.
- `429`: Too many requests (code `rate_limited`). A global per-IP budget of 300 requests/minute (burst 60) applies to every endpoint; login, signup, and test alerts have tighter dedicated limits.

---

[API](https://skmtc.dev/yoping/apis/yopingme-api.md) · [All operations](https://skmtc.dev/yoping/apis/yopingme-api/llms.txt) · [OpenAPI document](https://skmtc.dev/yoping/apis/yopingme-api/revisions/76d8deb40173?raw)