Skip to main content
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 and HTTP setup.

Parameters

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

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.

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. Selected response fields from IQRush Dev. Lists are shortened and project/run IDs are placeholders; this is not the full response.
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. 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 shows observed examples.