Stream probe run progress
Streams a probe run’s progress in real time as server-sent events until the run finishes.
Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.
Path Parameters
The agent this resource is scoped to (the UUID returned by createAgent / listAgents).
The probe run's id (returned by runProbe).
Response
SSE stream of probe progress (SimulateEvent frames).
The live simulate/chat SSE frame. It IS an AuditEventDTO: the SSE event: line equals eventType and the data: line is the AuditEventDTO JSON. Streams terminate with event: done or event: error, consumed via fetch() streaming.
On voice rows this is a MONOTONIC clock (relative), useless as an absolute time — use createdAtMs for wall-clock dating.
voice, chat, sms Authoritative AuditEvent / SimulateEvent event-type set. Each value selects the per-variant payload shape documented on AuditEventDTO.payload (see the *Payload schemas below). The legacy agent_utterance/turn_summary values are also supported for the ported audit_events write-path.
user_utterance, agent_message, tool_call, kb_retrieval, guardrail, verification, language_switch, handoff, barge_in, latency, filler, call_started, call_ended, error, agent_utterance, turn_summary, procedure_run, driver_state, claim_check Per-eventType payload (see schema description for the eventType→*Payload mapping).
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
- Option 10
- Option 11
- Option 12
- Option 13
- Option 14
- Option 15
- Option 16
- Option 17
Wall-clock insert time (audit_events.created_at) as epoch ms — the reliable timestamp for dating an event on the transcript. Present on persisted receipt rows; absent on the live SSE frame.