WEBSOCKET RUN (per-scenario URLs, bulk): Execute evaluators where each scenario carries its own websocket URL. Useful when you have a fleet of agents or stateful websocket sessions to test in a single batch.

Run-count: total conversations = len(scenarios) × frequency. (Personality and test-profile multipliers are not supported on this endpoint.)

frequency is required on this endpoint (no default).

When to use this vs others (pick the endpoint matching the agent's configured connection — check aiagents_retrieve):

• run_scenarios_text — single websocket URL or SMS/chat mode (simpler)
• run_scenarios — real voice / phone / SIP call
• run_scenarios_pipecat — Pipecat/Daily.co WebRTC deployment

Polling for completion: the response is the result itself — read its top-level id (status: 'running'). Poll GET /test_framework/v1/results/{result_id}/ until status is completed, failed, timeout or cancelled. A result stays non-terminal until every run has ended, then becomes completed if any run completed — even if runs failed their checks or others errored. To gate, require success_runs_count == total_runs_count (failed_runs_count counts only completed runs that failed evaluation).

Known limitation: result.run_type may show 'Text' instead of 'WebSocket' for runs triggered via this endpoint — this is a display issue only and does not affect execution.

{
  "runs": [
    {
      "number": "+11234567890",
      "inbound_number": "+11234567890"
    }
  ],
  "created_at": "2025-02-25T21:00:01.990052Z"
}