---
title: "Subscribe to events"
method: GET
path: "/events"
---

# Subscribe to events

`GET /events`

The events are sent as Server-Sent Events (SSE). Initially, the endpoint returns a list of events needed to reconstruct the current state of the conversation and the agent's status. After that, it only returns events that have occurred since the last event was sent.

Note: When an agent is running, the last message in the conversation history is updated frequently, and the endpoint sends a new message update event each time.

## Response `200`

OK

## Other responses

- `default` — Error

## Changes

- **2026-03-02** `44ca180606f9` — 1 breaking
  - added `subschema #1: Event agent_error` to the `items/` response property `oneOf` list for the response status `200`
- **2025-10-13** `e6147f7bdb93` — 1 breaking
  - the response property `errors` became nullable for the status `default`
- **2025-10-09** `4b8f63db02ed` — 1 info
  - added the required property `items/oneOf[subschema #2: Event status_change]/data/agent_type` to the response with the `200` status
- **2025-04-15** `d070058196c1` — 1 breaking, 1 info
  - removed the required property `items/oneOf[subschema #3: Event status_change -> subschema #2: Event status_change]/data/agent_type` from the response with the `200` status
  - removed `subschema #1: Event agent_error` from the `items/` response property `oneOf` list for the response status `200`

[Change history](https://skmtc.dev/coder/apis/agentapi/changes/events/get.md)

---

[API](https://skmtc.dev/coder/apis/agentapi.md) · [All operations](https://skmtc.dev/coder/apis/agentapi/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/coder/agentapi/revisions/b33e590af299/schema)