> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runreplay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

> Understand Replay public API error responses.

Replay uses standard HTTP status codes. Error responses include a `detail` field.

## Error format

```json theme={null}
{
  "detail": "Invalid API key"
}
```

## Status codes

| Status | Meaning               | Common cause                                                |
| ------ | --------------------- | ----------------------------------------------------------- |
| `401`  | Unauthorized          | Missing, inactive, or invalid API key.                      |
| `404`  | Not found             | The memory ID does not exist or belongs to another account. |
| `422`  | Validation error      | A request path or input is malformed.                       |
| `500`  | Internal server error | The API could not complete the request.                     |

## Troubleshooting

### `401 Unauthorized`

Check that your key is copied from the Replay web app account settings and sent with one of these headers:

```http theme={null}
Authorization: Bearer rpa_...
```

```http theme={null}
X-API-Key: rpa_...
```

### `404 Not found`

Check that the `memory_id` came from `GET /v1/memories` using the same API key.

### `500 Internal server error`

Retry the request. If it continues to fail, contact support with the endpoint, timestamp, and memory ID if one was used.