---
title: "Get test run history for a specific test"
method: GET
path: "/ai/assistants/tests/{test_id}/runs"
tags: ["Assistants"]
---

# Get test run history for a specific test

`GET /ai/assistants/tests/{test_id}/runs`

Retrieves paginated execution history for a specific assistant test with filtering options

## Path parameters

- `test_id` string, required

## Query parameters

- `status` string — Filter runs by execution status (pending, running, completed, failed, timeout)
- `page[number]` integer
- `page[size]` integer

## Response `200`

Returns paginated list of test runs for the specified test

- PaginatedTestRunList — Paginated list of test runs with metadata. Returns test run execution results with pagination support for handling large numbers of test executions.
  - `meta` Meta, required
    - `total_pages` integer, required
    - `total_results` integer, required
    - `page_number` integer, required
    - `page_size` integer, required
  - `data` TestRunResponse[], required — Array of test run objects for the current page.
    - `run_id` string, uuid, required — Unique identifier for this specific test run execution.
    - `test_id` string, uuid, required — Identifier of the assistant test that was executed.
    - `status` 'pending' | 'starting' | 'running' | 'passed' | 'failed' | 'error', required — Represents the lifecycle of a test: - 'pending': Test is waiting to be executed. - 'starting': Test execution is initializing. - 'running': Test is currently executing. - 'passed': Test completed successfully. - 'failed': Test executed but did not pass. - 'error': An error occurred during test execution.
    - `triggered_by` string, required — How this test run was initiated (manual, scheduled, or API).
    - `completed_at` string, date-time — Timestamp when the test run finished execution.
    - `logs` string — Detailed execution logs and debug information.
    - `conversation_id` string — Identifier of the conversation created during test execution.
    - `conversation_insights_id` string — Identifier for conversation analysis and insights data.
    - `test_suite_run_id` string, uuid — Identifier linking this run to a test suite execution batch.
    - `created_at` string, date-time, required — Timestamp when the test run was created and queued.
    - `updated_at` string, date-time — Timestamp of the last update to this test run.
    - `detail_status` TestRunDetailResult[] — Detailed evaluation results for each rubric criteria. Name is name of the criteria from the rubric and status is the result of the evaluation. This list will have a result for every criteria in the rubric section.
      - `name` string, required
      - `status` 'pending' | 'starting' | 'running' | 'passed' | 'failed' | 'error', required — Represents the lifecycle of a test: - 'pending': Test is waiting to be executed. - 'starting': Test execution is initializing. - 'running': Test is currently executing. - 'passed': Test completed successfully. - 'failed': Test executed but did not pass. - 'error': An error occurred during test execution.

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/team-telnyx/apis/telnyx-api.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api/revisions/e32d46c5945b/schema)