> ## Documentation Index > Fetch the complete documentation index at: https://docs.cekura.ai/llms.txt > Use this file to discover all available pages before exploring further. # Run Evaluator ElevenLabs > Execute evaluators against an ElevenLabs Conversational AI agent. Requires ElevenLabs credentials and `assistant_id` set to the ElevenLabs agent ID. ## OpenAPI ````yaml post /test_framework/v1/scenarios/run_scenarios_elevenlabs/ openapi: 3.1.0 info: title: Cekura API version: v1 description: >- Complete API documentation for the Cekura platform. This API provides endpoints for testing, observing, and evaluating AI voice agents — including managing agents, running evaluators, defining metrics, and analyzing call quality. servers: - url: https://api.cekura.ai security: [] paths: /test_framework/v1/scenarios/run_scenarios_elevenlabs/: post: tags: - Evaluators summary: Run evaluators against an ElevenLabs Conversational agent description: >- ELEVENLABS CONVERSATIONAL VOICE RUN: Execute evaluators against an ElevenLabs Conversational AI agent. The agent must have ElevenLabs credentials configured AND `assistant_id` set to the ElevenLabs agent ID. **Cost:** voice-simulation rate per run. **Run-count math:** total runs = `len(scenarios) × frequency × max(1, len(personality_ids)) × max(1, len(test_profile_ids))`. **When to use this vs others** (pick the endpoint matching the agent's configured connection — check `aiagents_retrieve`): - `scenarios_run_voice` — phone / SIP voice run - `scenarios_run_vapi_webrtc` — VAPI agents over WebRTC - `scenarios_run_retell_webrtc` — Retell agents over WebRTC - `scenarios_run_pipecat_v2` — Pipecat Cloud (project credentials, v2) operationId: scenarios-run-elevenlabs_2 requestBody: content: application/json: schema: $ref: '#/components/schemas/SchemaPostRunScenariosElevenLabs' examples: ElevenLabsRun: value: agent_id: 12 scenarios: - 101 - 102 frequency: 1 summary: ElevenLabs run application/x-www-form-urlencoded: schema: $ref: '#/components/schemas/SchemaPostRunScenariosElevenLabs' multipart/form-data: schema: $ref: '#/components/schemas/SchemaPostRunScenariosElevenLabs' responses: '200': content: application/json: schema: type: object properties: id: type: integer description: ID of the result agent: type: integer description: ID of the agent status: type: string enum: - running - completed - failed - pending - in_progress - evaluating - in_queue - timeout - cancelled - scaling_up description: >- Status of the result. Poll until it is `completed`, `failed`, `timeout` or `cancelled`. It stays non-terminal until every run has ended, then becomes `completed` if any run completed — even if runs failed their checks or others errored. run_as_text: type: boolean description: Whether the scenario ran as text or not example: false runs: type: array items: type: object properties: id: type: integer description: ID of the run status: type: string enum: - running - completed - failed - pending - in_progress - evaluating - in_queue - timeout - cancelled - scaling_up description: Status of the run scenario: type: integer description: ID of the scenario number: type: string description: >- For outbound runs (agent.inbound=False). The given number that must be called from the phone number configured in the cekura agent. example: '+11234567890' inbound_number: type: - string - 'null' description: >- For inbound runs (agent.inbound=True). The agent's configured phone number will receive calls from this number. example: '+11234567890' scenario_name: type: string description: Name of the scenario test_profile_data: type: - object - 'null' description: >- Details of the test profile associated with this run scenario outbound_dial_window_opens_at: type: - string - 'null' format: date-time description: >- When the outbound dial window opened (run transitioned to pending/waiting-for-call). Null until dispatched. outbound_dial_window_seconds: type: - integer - 'null' description: Duration of the outbound dial window in seconds. outbound_dial_window_closes_at: type: - string - 'null' format: date-time description: >- Deadline by which your agent must dial the outbound number (opens_at + outbound_dial_window_seconds). Dials after this are dropped and the run returns status: timeout. examples: - id: 274 status: pending scenario: 1 number: null inbound_number: '+11234567890' scenario_name: Customer Support Call (Agent Inbound = True) test_profile_data: null outbound_dial_window_opens_at: null outbound_dial_window_seconds: null outbound_dial_window_closes_at: null - id: 275 status: pending scenario: 2 number: '+11234567890' inbound_number: null scenario_name: Outbound Sales Call (Agent Inbound = False) test_profile_data: null outbound_dial_window_opens_at: '2026-06-24T10:47:30Z' outbound_dial_window_seconds: 300 outbound_dial_window_closes_at: '2026-06-24T10:52:30Z' created_at: type: string format: date-time example: '2025-02-25T21:00:01.990052Z' description: '' '400': content: application/json: schema: type: object properties: field_name: type: array items: type: string description: '' security: - api_key: [] - oauth2: [] - supabase_session: [] components: schemas: SchemaPostRunScenariosElevenLabs: type: object description: Schema for the run_scenarios_elevenlabs endpoint. properties: agent_id: type: integer description: ID of the agent to run evaluators for assistant_id: type: string writeOnly: true description: | Alternative to agent ID - the assistant ID to use for this scenario Example: `"asst_1234567890"` scenarios: type: array items: type: integer description: > List of evaluator IDs to run. Either scenarios, tags, or folder_path must be provided. Runs start in the order given. Example: `[11, 22, 33]` To run evaluators by tag or folder, use the `tags` or `folder_path` fields instead. tags: type: array items: type: string description: > List of tags to filter evaluators to run. Either evaluators or tags must be provided. Example: `["tag1", "tag2", "tag3"]` folder_path: type: string description: > Dot-separated folder path to select evaluators from (e.g. `"Sales.Inbound"`). Mutually exclusive with `scenarios` and `tags`. Requires `project_id`. project_id: type: integer description: > Project ID. Required when using `folder_path` (or when passing a folder path string via `scenarios`). Example: `1376` frequency: type: integer minimum: 1 default: 1 description: > The number of times each evaluator will run. Each repeat runs the whole list in order before the next one starts (A, B, A, B), rather than grouping repeats of one evaluator. Example: `1` name: type: string description: Label text for result outbound_phone_number: type: string description: | Override the phone number to use for outbound calls. Example: "+1234567890" personality_ids: type: - array - 'null' items: type: integer description: > List of personality IDs to override for this run. If not provided, uses the scenario's default personality. Example: `[123, 456, 789]` test_profile_ids: type: - array - 'null' items: type: integer description: > List of test profile IDs to override for this run. If not provided, uses the scenario's default test profile. Example: `[123, 456, 789]` personality_id: type: - integer - 'null' description: >- Single personality ID override. Merged into personality_ids; prefer personality_ids for multiple. test_profile_id: type: - integer - 'null' description: >- Single test profile ID override. Merged into test_profile_ids; prefer test_profile_ids for multiple. mode: enum: - same_number - different_numbers type: string x-spec-enum-id: 9ea0c9743bd9d873 default: same_number description: |- Using same or different phone numbers for each evaluation * `same_number` - same_number * `different_numbers` - different_numbers agent_number: type: string description: > Override the phone number from which the agent under test receives the call during outbound runs. This allows overriding the default agent contact number for testing purposes. Example: "+1234567890" concurrency_limit: type: integer minimum: 1 description: > Cap on the number of evaluator runs executed in parallel. Default: unbounded (subject to your provider's rate limits). Use this to avoid hitting provider rate limits on large frequency or folder runs. Example: `5` calls_per_second: type: - integer - 'null' maximum: 4 minimum: 1 description: >- Most calls started per second for this run, a whole number from 1 to 4. Leave unset for no limit. mock_tool_names: type: array items: type: string description: > Names of mock tools to activate for this run. Cekura swaps those tools' URLs to mock endpoints while the run is active and restores the originals when it finishes. Omit (or send null) to mock every tool configured on the agent; send an empty list to mock none so every tool keeps its original endpoint. Example: `["get_appointments", "cancel_booking"]` agent_version_id: type: string description: > Run against a stored version of the agent instead of the agent as it is live. Cekura makes a private copy of the agent in your provider account, puts that version's prompt on it, and runs against the copy — voice, model and tools stay as the agent is configured now, and the live agent is never changed. Accepts the version label shown in the agent's version history (`v12`, or `p1` for a version an improvement run proposed) or its numeric `history_id`. List them with `GET /test_framework/v1/aiagents/{id}/history/`; a version is usable when its `is_runnable` is true. Available for VAPI, Retell, ElevenLabs and Bland agents that are outbound and have a single prompt. Example: `"v12"` elevenlabs_agent_id: type: string description: >- ElevenLabs agent ID to test against. Overrides the agent's stored assistant_id for this run. elevenlabs_data: allOf: - $ref: '#/components/schemas/SchemaElevenLabsData' description: >- Per-run ElevenLabs overrides (e.g. elevenlabs_base_url_override). Credentials are read from the agent. SchemaElevenLabsData: type: object description: Per-run ElevenLabs overrides. Credentials are read from the agent. properties: elevenlabs_base_url_override: type: - string - 'null' description: >- Override the ElevenLabs base URL for this run (e.g. a regional or self-hosted endpoint). elevenlabs_environment: type: - string - 'null' description: >- ElevenLabs environment for this run, used to resolve the agent's environment variables (tool URLs, secrets, headers). Defaults to the environment saved on the agent, then to production. elevenlabs_branch_id: type: - string - 'null' description: >- ElevenLabs agent branch for this run. Defaults to the branch saved on the agent, then to the agent's default branch. securitySchemes: api_key: type: apiKey in: header name: X-CEKURA-API-KEY description: >- API Key Authentication. It should be included in the header of each request. oauth2: type: http scheme: bearer bearerFormat: JWT description: OAuth access token issued by Cekura for connected apps. supabase_session: type: http scheme: bearer bearerFormat: JWT description: Cekura dashboard session token. Not a customer API credential. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.