Skip to main content
GET

Headers

string
required
Your API key for authentication.

Path Parameters

string
required
The unique identifier of the call whose pathway events you want to retrieve.

Query Parameters

string
required
Set to 2 to receive the pathway events format documented here. Omitting it returns the deprecated legacy log format, which is being phased out — always pass v=2.

Response

The response is a JSON array of event objects, one per event in the call, ordered by sequence. See Pathway Call Events for the full catalog of event types and per-type payload shapes.
string
The call id. All events for one call share it.
number
The ordering key within the call. Always sort by sequence, not created_at. Gaps are normal and do not indicate missing data.
string
What happened. Either a standalone event (conversation.init, node.transition, transcript.user, transcript.assistant, node.tag, interrupt.early, interrupt.late, button.press, llm.action) or an operation event of the form operation.phase, where the operation is one of webhook, tool, kb, sms, scheduling, loop_condition, var_extraction, custom_code, transfer_pathway, transfer_call, unit_test and the phase is invoke, result, error, or warning (plus webhook.mapping for variable-mapping outcomes).
string | null
The pathway node that was active when the event fired. null before the first node is entered.
number | null
Correlation key for multi-event operations: a result, error, warning, or mapping event carries the sequence of the invoke event it belongs to. null when there’s nothing to correlate.
object | null
Event-type-specific data. Payload shapes for every event type are documented in Pathway Call Events.
string
ISO 8601 timestamp of the event. Use for timing display; use sequence for ordering.