Attribute Mentions
Per-run observations linking brands to attributes, with prominence.
GET /api/v1/attribute-mentions returns the evidence level of Brand
Perception: one row each time an answer associated a tracked brand with an
attribute. Labels come from attributes; the answer
itself is joinable through runs.
Filters
| Parameter | Meaning |
|---|---|
attribute_id | Restrict to one attribute. |
brand_id | Restrict to one brand. |
run_id | Restrict to one run's observations. |
since / until | Bounds for created_at (ISO timestamp). |
Standard parameters (limit, offset, format=csv) work as described in
Pagination, filtering, and errors.
Key fields
run_id: the answer the observation came frombrand_id: the brand the attribute was attached toattribute_id: the canonical attribute observedprominence: 0 to 100, higher when the attribute appears earlier and more centrally in the answercreated_at: when the observation was recorded
Rows are ordered by created_at descending with run_id, brand_id, and
attribute_id as tiebreaks, so offset pagination is stable. History is
bounded by the parent run's date, so backfilled classifications of old runs
stay within your plan's history window.
Example
curl -H "Authorization: Bearer $AEO_API_KEY" \
"https://app.citlyze.com/api/v1/attribute-mentions?brand_id=$BRAND_ID&since=2026-08-01"Use this resource to build your own attribute matrix, trace a sentiment shift to the runs that caused it, or export perception evidence for reporting.