---
title: "Page conversation history"
description: "Returns the conversation's newest events at or before through and before before: its saved events and what its replies streamed live (assistant, reasoning and tool_update, and attempt_reset, after…"
canonical: "https://www.cool.computer/docs/api-reference/operator/page-conversation-history"
---
# Page conversation history

> Returns the conversation's newest events at or before through and before before: its saved events and what its replies streamed live (assistant, reasoning and tool_update, and attempt_reset, after…

```http
GET https://api.cool.computer/api/operator/conversations/{id}/history
```

Returns the conversation's newest events at or before through and before before: its saved events and what its replies streamed live (assistant, reasoning and tool_update, and attempt_reset, after which the live content its turn showed before it no longer shows). Consecutive live events of one text block, or of one call's output, read as one event with the id of the last. The first page omits both parameters: through is then the conversation's newest event id, which the page returns as stream_cursor, and the page also holds the events of a running turn beyond limit, up to 10,000 more: past that it holds the turn's newest, its earliest text block may start part way through, and the older pages hold the rest. Each older page sends next_before as before and that same stream_cursor as through, so every page describes one snapshot. Follow the conversation live from that snapshot by opening a WebSocket to live_url with after=\<stream_cursor>.

## Authorization

- A Cool Computers API key, user access token, or claimed agent access token in the Authorization header. Follow https://www.cool.computer/auth.md for agent registration and https://www.cool.computer/authentication.md for direct user credentials.

## Parameters

- `id` (path, string, at least 1 characters, required): Operator conversation identifier.
- `before` (query, integer, at least 0): Return events before this event ID. Requires through; before without through is invalid_request.
- `through` (query, integer, at least 0): Return events at or before this event ID: the stream_cursor of the first page. Omitted, it is the current stream cursor. Above the current stream cursor is invalid_request.
- `limit` (query, integer, 1 to 100): Maximum number of events, before live events are joined; the first page also holds the rest of a running turn.

## Responses

- `200`: A page of conversation events.
  - `application/json` (object)
    - `events` (array of object, required)
      - `id` (integer, at least 1, required)
      - `conversation_id` (string, required)
      - `turn_id` (string, required)
      - `attempt` (integer, at least 0, required)
      - `sequence` (integer, at least 0, required)
      - `kind` (string, required)
      - `payload` (any, required): The event's kind-specific JSON payload.
      - `created_at` (string, date-time, required)
    - `has_more_before` (boolean, required)
    - `next_before` (integer, at least 0, required)
    - `stream_cursor` (integer, at least 0, required): The conversation's newest event id in this snapshot. Open live_url with after=\<stream_cursor> to continue after it.
    - `live_url` (string, uri, required): The conversation's live stream, a WebSocket. Connect with ?after=\<id>: this history's stream_cursor, or to resume, the id of the last event or up_to_date received. Send Authorization: Bearer and no Origin header. Each message is a JSON object with a type. {"type":"hello"} comes first. {"type":"event","event":{...}} carries an OperatorEvent, whose id is the one this history uses: apply events in id order and show an event seen in both once. A snapshot replaces the live text of its block, a tool_end the live output of its call, and an attempt_reset drops the live content its turn showed before it. {"type":"up_to_date","id":\<id>} means every event the stream holds was sent. The last message says what to do next: {"type":"reconnect"} connect again after the last id received; {"type":"reset"} the stream no longer holds what follows your cursor: read this history again and connect after its stream_cursor; {"type":"gone"} the conversation was deleted.
- `400`: Bad Request.
- `401`: Unauthorized.
- `404`: Not Found.
- `429`: Too Many Requests. If the problem code is api_request_rate_exceeded, wait for Retry-After seconds; other problem codes describe a separate limit.
- `500`: Internal Server Error.
- `default`: A machine-readable API error with a stable code and recovery instruction.

An error is an `application/problem+json` document with a stable `code`; [API errors](/docs/api-reference/errors) says how to handle one.

## Example

```sh
curl "https://api.cool.computer/api/operator/conversations/$PARAM_ID/history" \
  -H "authorization: Bearer $TOKEN"
```
