Use this file to discover all available pages before exploring further.
Test calls let you programmatically validate an agent against canned
scenarios. Each run produces a real call log
(billed at a test-call multiplier, typically 2×). Use runs for
one-shot tests and batches to execute the same scenario several
times concurrently.
Must be true — required to prevent accidental charges
Returns 201 Created with the run. Status starts at queued and
advances to completed or failed; poll the list endpoint or
GET /v1/calls/{call_id} once
call_id is set.Errors:
A batch executes the same scenario N times in parallel. The response
returns immediately with a batch in in_progress; poll the detail
endpoint for per-run results.
curl -X POST https://api.thunderphone.com/v1/test-call-batches \ -H "Authorization: Bearer sk_live_YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "target_type": "agent", "target_id": 12, "direction": "outbound", "run_count": 5, "stagger_seconds": 2, "scenario_prompts": [ "Ask about refunds.", "Ask for hours of operation.", "Complain about a delayed shipment.", "Ask to speak with a human.", "Ask an unrelated trivia question." ], "consent_to_charge": true }'
Returns the same batch shape as the create response — note run_ids
is a list of child-run ids, not nested run objects. Fetch each run via
GET /v1/test-calls?limit=... or by following the
call_id on each run to GET /v1/calls/{call_id}.