---
title: "Page through linked history including truthful expired evidence metadata"
method: GET
path: "/counterparties/{id}/history"
tags: ["Counterparties"]
---

# Page through linked history including truthful expired evidence metadata

`GET /counterparties/{id}/history`

## Request

- Base URL: `https://www.sanctionskit.com/api/v1`
- URL: `https://www.sanctionskit.com/api/v1/counterparties/{id}/history`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/sanctionskit/apis/sanctionskit-api/docs/counterparties/:id/history/get.ts> (a function with typed inputs; its response is checked against the schema)

Required API key scope: results:read.

## Path parameters

- `id` string, uuid, required

## Query parameters

- `limit` integer
- `cursor` string, uuid
- `kind` 'screenings' | 'cases' | 'monitors'

## Response `200`

Successful response. JSON object with the required data key. All properties marked required are present, including keys whose value may be null. Unmarked properties can be omitted; clients should tolerate additional response properties.

- object
  - `data` CounterpartyHistory, required
    - `items` union[], required
      - union
        - CounterpartyScreeningHistory: Counterparty history item when kind=screenings. Expired status is metadata, not a reconstructed result.
          - `id` string, uuid, required
          - `created_at` string, date-time, required
          - `expires_at` string, date-time, nullable, required
          - `status` 'potential_match' | 'no_match' | 'expired', required
          - `evidence_state` 'available' | 'expired', required
        - CounterpartyCaseHistory: Counterparty history item when kind=cases.
          - `id` string, uuid, required
          - `created_at` string, date-time, required
          - `decision` 'open' | 'confirmed' | 'dismissed', required
          - `business_disposition` 'pending' | 'allow' | 'restrict' | 'escalate', required
          - `review_state` string, required
          - `screening_id` string, uuid, required
          - `latest_screening_id` string, uuid, nullable, required
        - CounterpartyMonitorHistory: Counterparty history item when kind=monitors. Deleted monitors remain visible as history.
          - `id` string, uuid, required
          - `created_at` string, date-time, required
          - `name` string, required
          - `status` 'active' | 'paused' | 'deleted', required
          - `last_screening_id` string, uuid, nullable, required
          - `next_run_at` string, date-time, required
    - `total` integer, required
    - `nextCursor` string, nullable, required

## Other responses

- `400`: **invalid_request** — Correct the request fields, resource identifiers, JSON body or query parameters before retrying.
- `401`: **authentication_required** — Send Authorization: Bearer with a valid API key. An omitted header can produce authentication_required; invalid supplied credentials produce invalid_api_key. **invalid_api_key** — Use an active key for the intended environment.
- `403`: **permission_denied** — Ask an organization owner to grant the required role or API-key scope. **insufficient_scope** — Use a key with the scope stated in this operation.
- `404`: **not_found** — Check the identifier and selected environment. The resource must belong to your organization and remain available.
- `405`: **method_not_allowed** — Use a method in the Allow response header. OPTIONS lists supported methods; HEAD follows GET authorization and returns no body.
- `409`: **invalid_cursor** — Use nextCursor from this counterparty and the same history kind.
- `413`: **response_too_large** — Reduce the requested page size or use the documented segmented case archive. No evidence is silently truncated.
- `429`: **rate_limited** — Wait for the request window to reset and retry with backoff.
- `500`: **internal_error** — Retry with backoff. For writes reuse the same idempotency key and identical input; include requestId when contacting support.
- `503`: **temporarily_unavailable** — Honor Retry-After when present and retry with bounded backoff. Follow this endpoint’s retry contract; preserve the same key and input for idempotent writes. Contact support with requestId if the failure persists.

---

[API](https://skmtc.dev/sanctionskit/apis/sanctionskit-api.md) - [All operations](https://skmtc.dev/sanctionskit/apis/sanctionskit-api/llms.txt) - [OpenAPI document](https://skmtc.dev/sanctionskit/apis/sanctionskit-api/revisions/ee35d211051a?raw)
