---
title: "List API keys"
description: "Lists API key metadata using an owner access token. API keys are rejected with access_token_required."
canonical: "https://www.cool.computer/docs/api-reference/authentication/list-api-keys"
---
# List API keys

> Lists API key metadata using an owner access token. API keys are rejected with access_token_required.

```http
GET https://api.cool.computer/api/api-keys
```

Lists API key metadata using an owner access token. API keys are rejected with access_token_required.

## Authorization

- A WorkOS access token returned by the self-serve email authorization flow. A claimed agent access token is also accepted for creating an API key, and only for that. API keys are not accepted for API-key administration.

## Responses

- `200`: API key metadata.
  - `application/json` (object)
    - `api_keys` (array of object, required)
      - `id` (string, required)
      - `name` (string, required)
      - `obfuscated_value` (string, required)
      - `created_at` (string, date-time, required)
      - `last_used_at` (string or null, date-time)
      - `expires_at` (string or null, date-time)
- `401`: Unauthorized.
- `403`: A user access token from email sign-in (cool login) is required; API keys receive access_token_required.
- `429`: Too Many Requests. If the problem code is api_request_rate_exceeded, wait for Retry-After seconds; other problem codes describe a separate limit.
- `500`: Internal Server Error.
- `default`: A machine-readable API error with a stable code and recovery instruction.

An error is an `application/problem+json` document with a stable `code`; [API errors](/docs/api-reference/errors) says how to handle one.

## Example

```sh
curl "https://api.cool.computer/api/api-keys" \
  -H "authorization: Bearer $TOKEN"
```
