Skip to main content
POST
Mint a fresh test-type v2 conversation bound to an agent or team

Authorizations

x-api-key
string
header
required

Body

application/json

Mint a fresh session_type="test" chat session for the dashboard.

The agent-detail Test chat panel uses this. Identity is controlled by test_features.identity_resolution (default off): off mints a throwaway random end_user_id with NO identity-graph call, so dev-side Neo4j churn (wipes, merges, deletes) can never strand the panel with a stale uid; on, the session binds to the authenticated dashboard member's resolved internal:<clerk_user_id> EndUser, and every "Reset" / "End session" still mints a fresh Conversation row but reuses that same identity. Mirrors POST /v1/voice/web-call for text/API.

Bind to exactly one of a single Assistant (agent_id) or a Team (team_id + optional team_revision_id) — the same single-XOR-team invariant the runtime conversations table enforces. When team_id is given without team_revision_id, the handler resolves the team's active revision.

agent_id
string<uuid> | null
assistant_revision_id
string<uuid> | null
team_id
string<uuid> | null
team_revision_id
string<uuid> | null
tool_input_overrides
Tool Input Overrides · object | null
context_variables
Context Variables · object | null
test_features
TestSessionFeatureInput · object | null

Test-session feature toggles. Omitted means all off. The resolved snapshot is echoed back as test_features on TestChatStartResponse.

Response

Successful Response

session_id
string<uuid>
required
end_user_id
string<uuid>
required
test_features
TestSessionFeatures · object
required

Resolved, immutable snapshot persisted on a test conversation.