---
title: "Get Simulation Runs"
method: GET
path: "/v1/get-simulation-runs/{simulation_id}"
tags: ["Simulations"]
---

# Get Simulation Runs

`GET /v1/get-simulation-runs/{simulation_id}`

Get all simulation runs for a specific simulation.

## Path parameters

- `simulation_id` string, required

## Headers

- `X-API-Key` string, required

## Response `200`

Successful Response

- GetSimulationRunsResponse
  - `simulation_runs` SimulationRunRes[] — List of simulation runs
    - `id` integer, required — ID of the simulation run
    - `experiment_id` integer, required — ID of the simulation associated with the run
    - `summary` string, nullable — Summary of the simulation run
    - `tests_passed` integer, nullable — Number of tests that passed in the simulation run
    - `tests_failed` integer, nullable — Number of tests that failed in the simulation run
    - `total_tests` integer, nullable — Total number of tests in the simulation run
    - `tests_completed` integer, nullable — Number of tests that were completed in the simulation run
    - `curr_step_id` integer, nullable — Current step ID of the simulation run
    - `created_at` string, date-time, required — When the simulation run was created
    - `status` 'RUNNING' | 'COMPLETED', required — Enum representing the possible states of a simulation run. The taxonomy is intentionally minimal: a sim_run is either in-flight (RUNNING) or terminal (COMPLETED). The pass/fail/cancel distinction lives entirely on child test_result counters and statuses, not on sim_run. See livekit_agent/docs/test_result_status_redesign.md §2.2 for the full taxonomy.
    - `phone_number` string, nullable — Phone number of the simulation run

## Other responses

- `422` — Validation Error

---

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