> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iqrush.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Get a measurement run — HTTP

> Read execution status, data-family readiness, and available run counts.

Read execution status, data-family readiness, and available run counts.

**Method:** `GET`

**Path:** `/projects/{project_id}/runs/{run_id}`

Use the HTTP base for your authorized environment and an `Authorization: Bearer` header. See [authentication](/developers/guides/04-authentication) and [HTTP setup](/developers/guides/06-http-quickstart).

## Parameters

This table covers the standard read profile. It excludes internal application routes and advanced analysis controls.

| Name | Location | Type | Required | Default | Meaning |
| - | - | - | - | - | - |
| `project_id` | path | string | Yes | — | Project ID from list\_projects. Select the project in the intended workspace and environment. |
| `run_id` | path | string | Yes | — | Run ID from list\_runs for this project. Use the exact returned value and check readiness before reading measurements. |

## Request example

Set `IQRUSH_API_BASE` and `IQRUSH_ACCESS_TOKEN` through secure configuration. Replace project/run IDs and sample selections with values returned by your account. JSON objects and arrays are encoded as query strings.

```bash theme={null}
curl --fail-with-body --silent --show-error --get \
  --header "Authorization: Bearer ${IQRUSH_ACCESS_TOKEN}" \
  --header "Accept: application/json" \
  "${IQRUSH_API_BASE%/}/projects/${IQRUSH_PROJECT_ID}/runs/${IQRUSH_RUN_ID}"
```

## Read the response

Top-level fields include `status`, `data_ready`, `data_readiness`, and available count fields. Some counts are null. `results_stability` and `results_stability_detail` are not populated here.

Use a UUID returned by discovery. Request `get_results_stability` separately; do not use a null count as zero.

### Fields to use

These selected fields explain the example and the result to preserve. Field presence depends on the response; this is not a complete response schema.

| Field | Meaning and use |
| - | - |
| `status` | Execution state for this run. |
| `data_ready` | Summary data readiness; separate from statistical stability. |
| `completed_at` | Measurement completion timestamp. |
| `n_queries_submitted` | Submitted query count, not the number of returned answer statements. |
| `n_responses_pipeline` | Unpopulated in this edition. Preserve null as unavailable rather than reporting zero responses. |
| `results_stability` | Unpopulated in this endpoint. Request get\_results\_stability for quality assessment. |

Selected response fields from IQRush Dev. Lists are shortened and project/run IDs are placeholders; this is not the full response.

```json theme={null}
{
  "run_id": "RUN_ID",
  "status": "COMPLETED",
  "data_ready": true,
  "completed_at": "2026-09-24T18:23:55.508870+00:00",
  "n_queries_submitted": 240,
  "n_responses_pipeline": null,
  "results_stability": null
}
```

Read the actual returned scope, counts, and interval levels before interpreting these fields.

MCP equivalent: [`get_run`](/developers/tools/get_run). Use the parameters and defaults on this page for HTTP.

## If the result is unavailable

Check HTTP status and the response’s `error` field before using data. A successful empty response does not establish a zero value. Preserve `not_available`, `not_available_reason`, `unavailable_reason`, and `linked` where returned. [Errors and recovery](/developers/guides/13-errors) shows observed examples.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.