# Read definitions key api-keys

The ingestion keys minted on one record page: each key's name, prefix, scopes, when it was made, when it was last used and whether it is revoked. The SECRET is never here — it existed once, in the answer that minted it. Workspace admin, because key metadata is the page's shape. For what one key has actually been doing, read `get_definitions_key_api-keys_keyId_usage`.

Access class: `def:admin`.

## Endpoint

`GET /v1/definitions/{key}/api-keys`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| key | path | string | Yes |
| body | query | null | No |
| params | query | object | No |
| query | query | object | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": [
    {
      "boardId": "",
      "createdAt": "string",
      "id": "",
      "keyPrefix": "string",
      "lastUsedAt": "string",
      "name": "string",
      "scopes": [
        "string"
      ]
    }
  ]
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```