---
title: "Follow a conversation"
method: GET
path: "/v1/conversations/{id}/events"
tags: ["Conversations"]
---

# Follow a conversation

`GET /v1/conversations/{id}/events`

## Request

- Base URL: `https://api.shardflux.dev`
- URL: `https://api.shardflux.dev/v1/conversations/{id}/events`
- Auth: HTTP bearer

A server-sent event stream (`text/event-stream`) of the conversation as it runs. It never reaches the computer: it shows what the conversation reports.

`conversation`: the conversation, at the start and on every change. `transcript`: native transcript lines as they are stored (`session_id`, `file`, `offset`, `next_offset`, `size`, `data`). `delta`: live updates the harness streams while the conversation is followed (`seq`, `at`, `updates`: ACP session updates, e.g. `agent_message_chunk` for reply text as it is written, `tool_call`, `plan`); conversations in an ACP app stream them, terminal sessions report their transcript per message.

From now by default; `transcript_offset` (with `session_id`) and `after_seq` start earlier. Each event’s id is the stream’s cursor: reconnect with `Last-Event-ID` (EventSource does) to resume. A stream ends periodically; reconnect to continue.

## Path parameters

- `id` string, required

## Query parameters

- `transcript_offset` integer
- `session_id` string
- `after_seq` integer

## Response `200`

text/event-stream: `conversation`, `transcript` and `delta` events.

## Other responses

- `4XX`: Default Response
- `5XX`: Default Response

---

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