Find changes to investigate

Collect candidate citation-share and rank changes for follow-up. Method: GET Path: /projects/{project_id}/runs/{run_id}/significant-findings 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.

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.
`kinds`	query	string	No	`null`	JSON-encoded array string.
`min_effect_size`	query	number	No	`null`	Minimum absolute effect included in the findings selection; not a promise of business importance.
`brand_subset`	query	string	No	`null`	Select statements about self (the target brand), competitors, or all brands. Omission uses all.
`group_by`	query	string	No	`null`	JSON-encoded array. Split results into rows by the requested dimensions. Check both filters_applied.group_by and each row’s group_by_values before labeling the groups.
`filters`	query	string	No	`null`	JSON-encoded array. Select measured answers with objects containing dimension and values. Use labels from list_dimension_options; inspect returned warnings for filters that were not applied.
`reference`	query	string	No	`null`	JSON-encoded object. Choose the comparison run: previous_run, first_run, or specific_run. For specific_run, include run_id. The request’s run_id is the checkpoint.

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.

curl --fail-with-body --silent --show-error --get \
  --header "Authorization: Bearer ${IQRUSH_ACCESS_TOKEN}" \
  --header "Accept: application/json" \
  --data-urlencode 'kinds=["share_change"]' \
  --data-urlencode 'reference={"type":"previous_run"}' \
  "${IQRUSH_API_BASE%/}/projects/${IQRUSH_PROJECT_ID}/runs/${IQRUSH_RUN_ID}/significant-findings"

Read the response

Read data.findings, data.reference_run_id, and data.reference_type. Up to 50 findings include kind, subject, contrast, scope, and correction metadata. correction.method is none in this edition and family_size records the comparison family. These are exploratory candidates, not a set of confirmed changes. Broad screening increases chance findings. Use a specific follow-up question and retain the comparison limitations.

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.kinds`	Finding types requested for selection.
`data.findings[].kind`	Type of this finding, such as share_change.
`data.findings[].subject.domain`	Source associated with this finding.
`data.findings[].contrast`	Reference/checkpoint comparison with its difference and uncertainty. Read the kind before labeling the units.

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

{
  "data_ready": true,
  "data": {
    "kinds": [
      "share_change"
    ],
    "findings": [
      {
        "kind": "share_change",
        "subject": {
          "domain": "aad.org"
        },
        "contrast": {
          "value_a": 0.18162866582649265,
          "value_b": 0.15411077594718775,
          "diff": -0.027517889879304896,
          "ci_diff": {
            "lower": -0.049268835714634585,
            "upper": -0.0005404802297687744,
            "level": 0.95
          },
          "significant": true
        }
      }
    ]
  }
}

Read the actual returned scope, counts, and interval levels before interpreting these fields. MCP equivalent: get_significant_findings. 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.

Get started

Connect securely

Read measurements

Build dependable integrations

Build reports

Report recipes

Reference

Session and discovery

Visibility measurements

Sources and evidence

Changes and trends

Google data

Pages and report planning

HTTP operations

Find changes to investigate — HTTP

Parameters

Request example

Read the response

Fields to use

If the result is unavailable

​Parameters

​Request example

​Read the response

​Fields to use

​If the result is unavailable

Parameters

Request example

Read the response

Fields to use

If the result is unavailable