---
title: "Server-sent event stream of inbound activity"
method: GET
path: "/v1/events"
tags: ["Flows"]
---

# Server-sent event stream of inbound activity

`GET /v1/events`

## Request

- Base URL: `https://api.cadencercs.com`
- URL: `https://api.cadencercs.com/v1/events`
- Auth: HTTP bearer

For an application that wants to react to replies in its own process. **It requires holding the connection open** — if you would rather not, attach a `flow` and let Cadence answer, then read `GET /v1/conversations/{id}/answers`.

Events: `ready` on connect, `ping` every 15s, then `reply`, `fellback`, `help`, `optout` and `completed`. Scoped to conversations this key or account owns — `agentId` is a convenience filter, not a boundary.

## Query parameters

- `agentId` string

## Response `200`

An `text/event-stream`. Each event's `data` is the JSON below.

## Other responses

- `401`: Missing, unknown or revoked API key.
- `403`: Key suspended, or scoped to a different brand than the one addressed.
- `500`: Unexpected server error. The body is always JSON.

---

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