Brand24 is a listening product: it finds the posts and articles that name a brand and hands a team the stream. Trends API answers the question next to that one. Is demand for the phrase rising, on which platform, and by how much. The answer is a 0-100 series per source and one percent per growth window, from one POST. Teams replacing a listening seat they only ever used for charts land here. Teams that work the mentions themselves should keep the listening tool. The category view sits on Social listening API.
Two different objects: a stream and a score
A mention stream grows with the noise. Every item needs a reader, a tag, or a filter, and the count means little until someone decides what counts. A demand score is one row per week per platform. get_time_series with source tiktok and the brand phrase as keyword returns the curve; get_growth over 3M and 12M returns the direction. Storage is a table, not an inbox.
The report chart, automated
The monthly brand chart is where listening seats go to be underused. Pulled from this API, it is a scheduled job: four sources, one keyword, rows into the warehouse, percent into the deck. The recipe sits on Brand demand API. Only successful 200 responses count against quota; caps sit on pricing.
Where Brand24 still wins
Crisis work, journalist outreach, and community management need the posts themselves, with links and authors. No score replaces reading the room during a bad week. Keep the tool that owns the text. Add the score when the meeting asks whether the spike mattered, because that question has a numeric answer and this API is where it lives.