# List monitor captures

**GET** `/v1/monitors/{id}/captures`

## Parameters

- `id` (path, string, required)
- `limit` (query, integer)
- `cursor` (query, string) — Pagination cursor from a previous response.

## Responses

### 200 — Successful response.
- `data`
- `data.id`
- `data.monitor_id`
- `data.screenshot_id`
- `data.scrape_id`
- `data.image_url`
- `data.content_hash`
- `data.previous_hash`
- `data.hash_distance`
- `data.change_pct`
- `data.has_change`
- `data.title_changed`
- `data.outcome`
- `data.captured_at`
- `next_cursor`
- `has_more`

### 401 — Unauthorized. The request carried no valid credential, and no work was
performed. The unified `Error` envelope carries one of the codes below
in `error.code`; match on the code, never on the prose.

- `invalid_api_key` — a bearer API key was presented and rejected:
  unknown, revoked, expired or malformed. The bearer-only operations
  (`/v1/webhook-deliveries*` among them) also return it when no
  `Authorization` header is sent. `GET /v1/account` is the exception
  to "malformed": it returns `invalid_api_key` only for a key that
  starts `sk_test_` or `sk_live_` and is unknown, revoked or expired.
- `unauthorized` — the `Authorization` header is absent or malformed on
  an operation that also accepts a dashboard session (the dual-auth and
  billing operations). `GET /v1/account` also returns it, for no
  `Authorization` header and for any bearer value that does not start
  `sk_test_` or `sk_live_` (that value is checked as a dashboard
  session token).

Not retryable as-is: supply a valid API key first.
- `status`
- `error`
- `error.code`
- `error.message`
- `error.http_status`
- `error.failed_at`
- `error.details`