Skip to main content
GET
Retrieve a test result

Authorizations

X-CEKURA-API-KEY
string
header
required

API Key Authentication. It should be included in the header of each request.

Path Parameters

id
integer
required

A unique integer value identifying this result.

Response

agent
integer
required
id
integer
read-only
name
string

Name of the result Example: "Test Result 1"

Maximum string length: 255
agent_name
string
read-only

Name of the agent associated with this result

agent_version
string
read-only

The agent version (history record) this result ran against, or null.

status
enum<string>
read-only

Current status of the result

  • running - Running
  • completed - Completed
  • failed - Failed
  • pending - Pending
  • in_progress - In Progress
  • evaluating - Evaluating
  • in_queue - In Queue
  • timeout - Timeout
  • cancelled - Cancelled
  • scaling_up - Scaling Up
Available options:
running,
completed,
failed,
pending,
in_progress,
evaluating,
in_queue,
timeout,
cancelled,
scaling_up
met_expected_outcome_count
string
read-only

Number of runs that fully met their expected outcomes with a score of 100

total_expected_outcome_count
string
read-only

Total number of runs that had expected outcomes defined

success_rate
number<double>
read-only

Success rate of the test runs

run_as_text
boolean
read-only

Whether this test was run in text mode instead of voice mode Example: true or false

is_cronjob
string
read-only

Whether this result was created by a scheduled cronjob

runs
object
read-only

Run objects keyed by run ID string (e.g. {"12345": {...}}). The list endpoint returns runs as an array of summaries instead.

overall_evaluation
any | null

Overall evaluation of the test runs Example:

total_duration
string
read-only

Total duration of the test runs for this result Example: 22:30

total_runs_count
string
read-only

Total number of test runs associated with this result Example: 10

completed_runs_count
string
read-only

Number of test runs that have completed successfully Example: 10

success_runs_count
string
read-only

Number of test runs that were marked as successful Example: 10

failed_runs_count
string
read-only

Number of test runs that failed or encountered errors Example: 10

connected_runs
string
read-only

List of run IDs that got connected successfully (have transcript data). Returns empty list if no connected runs.

failed_infrastructure_runs
string
read-only

List of run IDs that failed infrastructure issues metric (score=0). Returns null if metric not found, empty list if metric exists but no failures.

failed_workflow_runs
string
read-only

List of run IDs that failed expected outcome metric (score=0). Returns null if metric not found, empty list if metric exists but no failures.

successful_calls
string
read-only

List of run IDs that completed successfully. Returns empty list if no successful runs.

scenarios
string
read-only

List of scenario names used in the test runs for this result Example: ```

critical_categories
string
read-only

List of critical categories for this result Example:

metrics
string
read-only
runs_by_tags
string
read-only
latency_data
string
read-only
failed_reasons
any | null

Failed reasons of the test runs Example:

ai_summary
any | null

LLM-generated narrative summary of the result, structured for the Results-page UI. Example:

ai_summary_status
string
read-only

Generation state of the async AI summary, derived so the UI can show a reliable state instead of guessing from an empty ai_summary. completed = summary populated; skipped_no_failures = no failed runs, nothing to summarize; pending = there are failed runs but the summary isn't ready yet (still generating).

next_steps
any | null

LLM-suggested next steps to fix the issues found in this result, ordered by impact. Example:

performance_metrics
string
read-only

Per-rubric-rule performance breakdown. One entry per rule in the project's rubric_config: metric name, aggregated value across the result's runs, and whether that aggregate meets the rule's conditions.

run_type
string | null
read-only

Run Execution Type

run_settings
any | null

Snapshot of the override-relevant request payload (personality_ids, frequency, concurrency_limit, connection-specific overrides, etc.).

created_at
string<date-time>

Timestamp when this test result was created Example: 2021-01-01 00:00:00

updated_at
string<date-time>
read-only

Timestamp when this test result was last updated Example: 2021-01-01 00:00:00