List trace events grouped by trace
fromDate and toDate are required. fromDate is included in the results and
toDate is not, so a full day is
fromDate=2026-08-05T00:00:00Z&toDate=2026-08-06T00:00:00Z.
To page through results, pass the nextCursor value from the previous response
back as cursor. Keep every other parameter the same — a cursor is tied to the
filters, data mode, and sort order it was created with, and changing any of them
makes it invalid.
To fetch one specific event, filter by eventId. There is no separate
single-event endpoint.
If you request an event name this API does not support, it is ignored rather
than rejected, and listed back to you in meta.unsupportedEventNamesRequested.
Authorizations
Project-bound API key. Do not send an Authorization header.
Path Parameters
1Query Parameters
How many events to return. Counted before events are grouped into traces, so a page of 100 events may contain fewer than 100 traces.
1 <= x <= 10000Pass the nextCursor value from the previous response to get the next page.
Keep all other parameters unchanged.
1Filter by category of event. Pass one or more values, comma-separated or by
repeating the parameter. An unrecognised value is rejected with 400.
Each category covers a fixed set of event names: llm covers
llm.call.completed; tool covers tool.call.completed and
tool.call.skipped; decision covers agent.decision; and error covers
both failure events, llm.call.failed and tool.call.failed.
4llm, tool, decision, error Filter by specific event name, when eventTypes is broader than you need.
Pass up to 20 values, comma-separated or by repeating the parameter.
Unrecognised names are not rejected. They are ignored and returned to you in
meta.unsupportedEventNamesRequested, so only the names listed below will
actually select data.
20llm.call.completed, llm.call.failed, tool.call.completed, tool.call.failed, tool.call.skipped, agent.decision Filter to specific sessions. Pass up to 10,000 session IDs, comma-separated or by repeating the parameter.
100001Return only the event with this ID.
1Return only events belonging to this trace.
1Filter to events produced by this agent. Matched exactly; agent names are set by whoever built the project, so there is no fixed list.
1Filter agent decision events by the kind of decision made, for example
routing or escalation.
Matched exactly, and not restricted to a fixed list — new decision kinds can be added by the platform at any time, so an unrecognised value returns no results rather than an error. The values below are the ones currently in use.
1Filter by the channel the conversation took place on. Pass a single value; if you repeat the parameter only the first value is used, and a comma-separated list is treated as one literal value rather than a list.
Matched exactly as stored, with no alias handling. This differs from the
sessions endpoint, which accepts shorthand such as web or sms and
expands it. Here you must use the exact channel name: web_chat rather than
web, twilio_sms rather than sms, and the specific voice channel such
as voice_vxml or audiocodes rather than voice.
Not restricted to a fixed list, so an unrecognised value returns no results rather than an error, and a newly added channel works before the list below is updated.
http_async, slack, line, msteams, whatsapp, messenger, instagram, twilio_sms, zendesk, telegram, genesys, genesys_open_messaging, ai4w, kore_agent_assist, email, voice_vxml, korevg, audiocodes, genesys_audio_connector, voice_pipeline, voice_realtime, voice, voice_twilio, voice_livekit, ag_ui, a2a, sdk_websocket, web_debug, web_chat, api, http Filter by the environment the events were recorded in. Pass a single value; if you repeat the parameter only the first value is used.
Matched exactly as stored. Not restricted to a fixed list, so an unrecognised value returns no results rather than an error.
dev, staging, production, working-copy Set to true to return only events that failed, or false for only those
that succeeded. Omit to return both. Accepts true, false, 1, or 0.
How much detail to return per event. summary returns the key facts. full
adds the complete request and response content under
eventData.payloadData.
summary, full asc, desc Response
Trace event page returned successfully.