Test-fires one of the session agent's triggers into the sandbox.
The agent reacts to the trigger with its real output-destination send (and any mid-run send) captured / hard-blocked — the captured reply and blocked notices arrive on the stream / messages endpoints, same as a participant turn. Only bindings selecting the session's agent fire. Sandbox sessions only; a real fire belongs on `POST /triggers/{trigger}:fire`.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The session id returned by open.
The tenant identifier
The trigger to fire and an optional sample payload.
The trigger to fire. Must be bound to the session's agent.
uuidOptional synthesized event body for IntegrationEvent triggers — nests
under TriggerFirePayload.Body["payload"], same as
POST /triggers/{trigger}:fire. Rejected (400) for other kinds.
Optional per-fire overrides of the resolved agent input, keyed by
parameter name (e.g. user_query). Applied after the binding's
mappings resolve, so each entry wins over the resolved value — even a
LITERAL mapping. Lets an operator test a trigger-driven run with
specific input from the debug console without editing the persisted
binding. Sandbox-only; never persisted. Unset (or omitting a parameter)
reproduces the binding's resolved input exactly.
How a step runs async operations (subtask, consult, human-approval, external callback).
"UNSPECIFIED" | "AGENT_DECIDES" | "FORCE_AWAIT" | "FORCE_BACKGROUND"Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/fruxon/sessions/string/triggerFires" \ -H "Content-Type: application/json" \ -d '{}'{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}