Get events
get_eventsRead-onlyIdempotent
Page through events from across the org or one resource.
Instructions
Page through events from across the org or one resource.
Pass ``id="<type>:<uuid>"`` to narrow to a single resource —
supported types are ``call``, ``email``, and ``sms`` (e.g.
``id="sms:<uuid>"`` after ``send_sms``). When narrowed to a
call, the response includes a ``call_status`` field reflecting
the call's current state. Without ``id``, returns events from
across the whole org. ``kind`` filters server-side by event kind
(``state_change``, ``agent_turn``, ``user_turn``, ``tool_call``,
``error``, ...).
This is **not** a streaming subscription — the call returns
whatever events exist now plus a ``next_cursor`` if more pages
remain. To follow a call to completion, loop: pass the previous
response's ``next_cursor`` until ``next_cursor`` is null and,
when narrowed to a call, ``call_status`` is one of
``completed``, ``failed``, ``busy``, ``no_answer``, ``canceled``
(the terminal set).
Example:
get_events(id="call:0c2f...-...", limit=200)
Returns ``{"items": [...], "next_cursor": <str|None>,
"call_status": <str|None>}`` on success, or
``{"error": ...}`` on a malformed ``id`` or upstream failure.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| kind | No | ||
| limit | No | ||
| cursor | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||