List campaign runs
Recent execution history for this agent’s campaign: one row per processed call — who was called, when, the outcome the call reached, and whether the post-call workflow succeeded — plus the leads still queued for a future dial. This is not GET /api/call-history, which lists calls; a run is a call plus what the workflow did with it. Filter by name or phone to answer questions about one lead. Customer role: agency_admin.
Required API key scope: calls:read.
Authorizations
Send your API key as Authorization: Bearer YOUR_API_KEY.
Path Parameters
Agent id returned by the Agents API.
1Query Parameters
Pair with campaignId; omit both for primary campaign.
1Pair with locationId; omit both for primary campaign.
1Filter by contact id.
Filter by lead phone number.
Filter by lead name.
Inclusive start of the run-start-time window. A UTC ISO 8601 timestamp is canonical; a plain YYYY-MM-DD date is accepted and read as that day at 00:00:00Z. A timestamp must carry Z or an explicit offset, since one without a zone would be read as server-local time and shift the window. An empty string clears the bound. Anything else is a 400 rather than a silently wrong window.
Inclusive end of the run-start-time window. A UTC ISO 8601 timestamp is canonical; a plain YYYY-MM-DD date is accepted and covers that whole day, through 23:59:59.999Z. A timestamp must carry Z or an explicit offset, since one without a zone would be read as server-local time and shift the window. An empty string clears the bound. Anything else is a 400 rather than a silently wrong window.
Maximum number of runs to return.
1 <= x <= 200