Read mention scores — HTTP

Read how often an entity is named, or its recorded mention count. Method: GET Path: /projects/{project_id}/runs/{run_id}/mention-score 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.
`metric`	query	string	No	`"count"`	coverage requests how often responses mention the entity; count requests mention occurrences. Coverage is a proportion; count is a tally.
`aggregation_level`	query	string	No	`"bundle"`	entity selects individual measured names; bundle requests configured brand groupings. Coverage is served at entity level even when bundle is requested; read served_aggregation_level.
`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.
`subject`	query	string	No	`null`	JSON-encoded object. Choose brands with kind: leaderboard, all, self, self_and_competitors, or specified. For specified, provide entities_or_bundles. An unmeasured name is not a measured zero.

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 metric=coverage \
  --data-urlencode aggregation_level=entity \
  --data-urlencode 'group_by=["platform"]' \
  --data-urlencode 'subject={"kind":"specified","entities_or_bundles":["Colorescience"]}' \
  "${IQRUSH_API_BASE%/}/projects/${IQRUSH_PROJECT_ID}/runs/${IQRUSH_RUN_ID}/mention-score"

Read the response

Measurement envelope with data.metric, data.rows, and data.served_aggregation_level when supplied. Rows include entity_or_bundle, group_by_values, estimate, and brand flags. Coverage requested at bundle level is served at entity level in this edition. Do not sum alias coverage. Counts can carry confidence intervals; keep any interval returned even if an older tool description says otherwise.

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.served_aggregation_level`	Reporting unit actually served. It can differ from the requested bundle grouping for coverage.
`data.rows[].entity_or_bundle`	Measured name or grouping represented by this row.
`data.rows[].estimate.value`	Mention coverage as a proportion, or mention count as a tally, according to data.metric.
`data.rows[].estimate.n_responses`	Response count provided for coverage; do not substitute estimate.n as a universal denominator.
`data.rows[].estimate.stability`	Row quality. It does not replace the run-level convergence result.
`data.filters_applied.warnings`	Requested scope or data limitations to retain with the result.

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": {
    "metric": "coverage",
    "aggregation_level": "entity",
    "served_aggregation_level": "entity",
    "rows": [
      {
        "entity_or_bundle": "Colorescience",
        "group_by_values": {
          "platform": "VERTEX"
        },
        "estimate": {
          "value": 0.39166666666666666,
          "ci": {
            "lower": 0.3320830242376262,
            "upper": 0.4546636584163782,
            "level": 0.95
          },
          "n": 94,
          "n_responses": 240,
          "stability": "stable",
          "stability_n": 240
        }
      }
    ],
    "filters_applied": {
      "filters": {},
      "group_by": [
        "platform"
      ],
      "warnings": []
    }
  }
}

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

Read mention scores — 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