> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Events and streaming responses

> Some APIs return a bounded event page. Notebook cell events and assistant turns also expose server-sent event streams. These are observation APIs; listening does not itself cancel 

How-to guideApplies to: Unified engine deployments

Some APIs return a bounded event page. Notebook cell events and assistant turns also expose server-sent event streams. These are observation APIs; listening does not itself cancel or repeat execution.

## Read event pages

Notebook output pages use cell execution IDs and sequence cursors. The matching cell-events endpoint streams server-sent events. A document cell ID is not a cell execution ID. Assistant event pages use a turn and an `after` sequence. Read the reference page for the exact cursor.

Save the last sequence when building a client that reconnects. Read the execution's status as well as its events; an empty page does not always mean completion.

## Watch assistant SSE

The assistant event stream uses `text/event-stream`. The stream emits event IDs and a completion event when appropriate. Reconnect with `Last-Event-ID` or the supported `after` query parameter.

The example caps stream size and watch duration. **Stop watching** closes the local connection. To stop the turn, call its cancel endpoint and inspect its state.

## Handle interrupted observation

An interrupted stream does not imply a failed turn. Reconnect using the saved sequence or read the turn directly. Do not submit the same question as a new turn just to recover its existing events.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.