Skip to main content
POST
/
agents
/
{agentId}
/
simulate
Error
A valid request URL is required to generate request examples
{
  "id": "<string>",
  "conversationId": "<string>",
  "seq": 123,
  "tsMs": 123,
  "payload": {
    "text": "<string>",
    "isFinal": true,
    "language": "<string>",
    "asrConfidence": 123
  },
  "traceId": "<string>"
}

Authorizations

​
Authorization
string
header
required

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

​
agentId
string
required

Body

application/json

Chat/voice draft tester request. mode selects the tester surface: text (in-UI chat tester) or voice (in-browser voice draft tester); voice_browser/probe_loopback also supported. draftMode runs the simulation against the ephemerally compiled draft config (default true for the in-builder tester).

​
mode
enum<string>
required
Available options:
text,
voice,
voice_browser,
probe_loopback
​
scenarioId
string
​
draftMode
boolean

Run against the ephemerally-compiled draft config (not the published version, not billed). Default true for the in-builder chat/voice tester.

​
transcript
string[]

Response

SSE stream of SimulateEvent.

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.

​
id
string
required
​
conversationId
string
required
​
seq
integer
required
​
tsMs
integer
required
​
channel
enum<string>
required
Available options:
voice,
chat
​
eventType
enum<string>
required

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.

Available options:
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
​
payload
object
required

Per-eventType payload (see schema description for the eventType→*Payload mapping).

​
traceId
string