> ## 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.

# Read measured queries — HTTP

> Read the actual questions included in a run.

Read the actual questions included in a run.

**Method:** `GET`

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

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. |
| `prompt_type` | query | string | No | `null` | Select an exact Category facet label returned for the project. |
| `intent` | query | string | No | `null` | Select an exact Customer Intent facet label returned for the project. |
| `topic` | query | string | No | `null` | Select an exact measured topic label. A broader phrase does not select every topic containing that phrase. |
| `entity` | query | string | No | `null` | Exact entity name for checking whether it was mentioned in a query’s responses. |
| `limit` | query | integer | No | `50` | Maximum query rows to return. Check n\_returned, n\_available, and truncated; this operation has no cursor. Minimum 1. Maximum 200. |

## 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" \
  --data-urlencode entity=Colorescience \
  --data-urlencode limit=50 \
  "${IQRUSH_API_BASE%/}/projects/${IQRUSH_PROJECT_ID}/runs/${IQRUSH_RUN_ID}/queries"
```

## Read the response

`data.rows` contains query text and labels. `data.n_total_run` is the full run total; `subject_summary` describes the selected and returned counts. With a measured `entity`, rows can include `mentioned`.

This is a qualitative query lookup with no scores. `limit` caps the result and there is no pagination cursor. An unindexed entity does not receive a measured presence claim.

### 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 |
| - | - |
| `data.rows[].topic` | Measured topic assigned to the query. |
| `data.rows[].prompt_type` | Category facet label assigned to the query. |
| `data.rows[].intent` | Customer Intent label assigned to the query. |
| `data.rows[].mentioned` | When checking a measured entity, whether its mentions were found for this query. Inspect unindexed-name warnings first. |
| `data.n_returned` | Rows returned after the request limit. |
| `data.n_available` | Query rows matching the selection before the limit. |
| `data.n_total_run` | Query rows across the full run, before the selection. |
| `data.truncated` | Whether the response omitted matching rows because of its limit. |

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

```json theme={null}
{
  "data_ready": true,
  "data": {
    "rows": [
      {
        "topic": "Tinted Mineral Face SPF",
        "prompt_type": "what to look for",
        "intent": "commercial",
        "mentioned": false
      }
    ],
    "n_returned": 50,
    "n_available": 240,
    "n_total_run": 240,
    "truncated": true,
    "limit": 50
  }
}
```

Text and record identifiers are omitted from this excerpt. Retrieve those fields from your own response when preparing an evidence review.

MCP equivalent: [`list_queries`](/developers/tools/list_queries). 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.