---
title: "Trigger a manual test run"
method: POST
path: "/ai/assistants/tests/{test_id}/runs"
tags: ["Assistants"]
---

# Trigger a manual test run

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

Initiates immediate execution of a specific assistant test

## Path parameters

- `test_id` string, required

## Request body

- TriggerTestRunRequest — Request model for triggering a single test run. Optional request body for the trigger test run endpoint.
  - `destination_version_id` string — Optional assistant version ID to use for this test run. If provided, the version must exist or a 400 error will be returned. If not provided, test will run on main version

## Response `201`

Returns the created test run with execution details and status

- TestRunResponse — Response model containing test run execution details and results. Provides comprehensive information about a test execution including status, timing, logs, and detailed evaluation results.
  - `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-2.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api-2/revisions/8f5f4e537994/schema)