Test an agent with a draft revision via SSE streaming
Streams a draft-revision test run as Server-Sent Events (SSE) — the same event protocol as `:stream`, but executed against the inline draft flow in the request rather than a published revision.
API-Only Endpoint
This endpoint is available via API only and requires authentication using the X-API-KEY header.
Fill in your parameters below and the code samples will update automatically.
To generate an API key, see the Settings guide.
Authorization
Bearer ApiKey JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
API key passed in the X-API-KEY header. Generate one from the Fruxon settings.
In: header
Path Parameters
The unique identifier of the agent
The tenant identifier
The test request including revision and parameters
Assets (files / knowledge sources) made available to the draft flow for this test run.
Represents a sequence of steps in a agent flow, supporting versioning and ordered execution.
A valid flow has exactly one ENTRY_POINT step and exactly one
EXIT_POINT step in Steps — these are not synthesized
for you. The other steps (AGENT, TOOL, CLAUDE_BOX)
sit between them, wired by Edges.
The parameter schema for this test run — name, type, required-ness,
default values. This is the authoritative declaration the engine
uses to resolve {{param.x}} placeholders against
Parameters at run time.
EntryPointFlowStep.parameters on the flow holds the same
shape and serves the UI / agent introspection; the runtime reads
the request-level parametersMetadata here. For consistency,
populate both with the same list.
List of additional sub-abents used by the flow during execution. These are referenced from within steps in the flow.
Key-value pairs of actual input values provided for the parameters.
File attachments included with the test request.
Integration configs to use for this test run, overriding the ones pinned on the draft revision. Lets the caller swap in different credentials or routing without modifying the draft.
Agent-wide default integration config per integration id used for this test run. See Fruxon.Model.Agents.AgentRevision.IntegrationBindings.
LLM provider configurations (API keys, etc.) to use for this test.
Number of the existing agent revision this draft is based on —
the test run resolves masked secrets (API keys, credentials) by
looking them up in that revision's stored
integrationConfigs / llmConfigs.
Set to 0 (the default) when there is no base revision —
e.g. a brand-new agent with no published revision yet. With
0, no secret resolution happens; any config the draft
references must carry its secrets inline.
int64Selects which integration-config variant an execution uses. Sandbox falls
back to production per-config when no sandbox variant is configured.
Callers normally send PRODUCTION or SANDBOX;
UNSPECIFIED is the zero value and exists only so the field can
be omitted on the wire without misrepresenting the user's intent —
the host DTO supplies the real default (typically PRODUCTION).
"UNSPECIFIED" | "PRODUCTION" | "SANDBOX"Optional session ID to use for testing. If null, a new session may be generated.
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/agents/string:streamTest" \ -H "Content-Type: application/json" \ -d '{}'"string"{
"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
}Executes an agent using its currently deployed revision with streaming output.
Returns results as Server-Sent Events (SSE) for real-time progress updates.
Test an agent with a draft revision
Executes the agent using a specific draft revision for testing purposes. This allows validating changes before publishing.