Read telemetry events for a browser session
Reads a page of telemetry events for the browser session. To page through results, pass the X-Next-Offset value from the previous response as offset and repeat while X-Has-More is true. Returns an empty list when telemetry data is unavailable.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Browser session ID
Query Parameters
Opaque pagination cursor: pass the X-Next-Offset value from the previous response to fetch the next page. When set, paging continues from this cursor and since is ignored, while until still bounds the page. It is not an event's seq field, so do not derive it from the response body.
x >= 0Start of the window: an RFC-3339 timestamp, or a duration like 5m meaning that long ago. Defaults to 5m. Ignored when offset is set.
End of the window (exclusive): an RFC-3339 timestamp, or a duration like 5m meaning that long ago.
Maximum number of events per page. Defaults to 20.
1 <= x <= 100Restrict results to these event categories. Repeat the parameter for multiple values.
console, network, page, interaction, control, connection, system, screenshot, captcha, monitor Read direction. asc (default) reads oldest first, starting from since or the offset cursor. desc reads newest first: each request returns one page of up to limit records ending at the offset cursor (or until, or the newest archived event); combining desc with since is rejected with a 400. In either direction the category filter applies within the page, so a filtered page may be empty while X-Has-More is true.
Response
A page of telemetry events.
Process-monotonic sequence number assigned by the browser VM. Pass as Last-Event-ID on reconnect to resume without gaps. Gaps in received seq values indicate dropped events.
x >= 1Union type representing any browser telemetry event. Discriminated on type. Each event's category determines when it is captured. The CDP collector-health events (monitor_disconnected, monitor_reconnected, monitor_reconnect_failed, monitor_init_failed) use the monitor category, which is not user-configurable: it flows automatically whenever any CDP category (console, network, page, interaction) is captured, and is silent otherwise. monitor_screenshot uses the opt-in screenshot category. All other event types are controlled by their per-category enable/disable flags.
- console_log
- console_error
- network_request
- network_response
- network_loading_failed
- network_idle
- page_dom_content_loaded
- page_load
- page_tab_opened
- page_layout_shift
- page_lcp
- page_layout_settled
- interaction_click
- interaction_key
- interaction_scroll_settled
- monitor_screenshot
- monitor_disconnected
- monitor_reconnected
- monitor_reconnect_failed
- monitor_init_failed
- Option 23
- Option 24
- Option 25
- Option 26
- Option 27
- Option 28
- Option 29
- Option 30