# What one board key has done lately

The last 30 days of one key minted on a custom board: calls per day, the routes it hit with counts and failures, failures by class, and when the key was last used. Reach for it when an integration has stopped writing and nobody knows whether it is still calling. Manage on the board; the pack-page twin is `get_definitions_key_api-keys_keyId_usage`.

Access class: `board:manage`.

## Endpoint

`GET /v1/boards/{id}/api-keys/{keyId}/usage`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| id | path | string | Yes |
| keyId | 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": {
    "answer": {
      "filters": {},
      "retention": "string",
      "since": "string",
      "sink": "string",
      "total": 1.5,
      "truncated": true
    },
    "failures": [
      {
        "count": 1.5,
        "failures": 1.5,
        "lastSeen": "string",
        "value": "string"
      }
    ],
    "key": {
      "id": "",
      "lastUsedAt": "string"
    },
    "perDay": [
      {
        "count": 1.5,
        "day": "string",
        "failures": 1.5
      }
    ],
    "routes": [
      {
        "count": 1.5,
        "failures": 1.5,
        "lastSeen": "string",
        "value": "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"
}
```
