Skip to main content
POST
Create QA run

Authorizations

Authorization
string
header
required

API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access.

Body

application/json
pack
enum<string>
required
Available options:
full,
language_hallucinations,
resolution_sentiment,
performance_trends
from_at
string<date-time>
required
to_at
string<date-time>
required
name
string

Optional cohort display name

Maximum string length: 120
assistant_ids
string<uuid>[]
filters
object
resolution_criteria
string

What counts as a successful resolution for this cohort

Maximum string length: 4000

Response

Created