How to monitor your brand reputation#

Brand reputation monitoring on APITube is four moves against /v1/news/everything and its siblings: pull every article that names your brand, measure the tone directed at your brand with entity.sentiment, count how that volume shifts over time with /v1/news/count, and stream new coverage live so nothing surprises you. Start with one mention query and layer the rest on top of the same filters.

curl "https://api.apitube.io/v1/news/everything?organization.name=Tesla&language.code=en&api_key=YOUR_API_KEY"

Send the key as a header (X-API-Key: YOUR_API_KEY) if you prefer not to put it in the query string. Results come back newest-first, because the default sort.by is published_at and the default sort.order is desc — so the freshest mention is already at the top without adding a sort.

How do I pull every article that mentions my brand?#

Add one entity filter to /v1/news/everything: organization.name for a company, or brand.name for a consumer brand. APITube resolves the name against the entities it tracks and returns only articles that mention it. Each filter accepts up to three comma-separated values, so you can watch a company and its product lines in a single request. If a name is not tracked or is misspelled you get a “not found” error — switch to the numeric entity.id, which is stable for a given brand and never changes.

curl "https://api.apitube.io/v1/news/everything?brand.name=Nike,Jordan&language.code=en&per_page=100&api_key=YOUR_API_KEY"

per_page goes up to 250, so a wide sweep of recent coverage fits in one call. To find the right entity.id for a brand, query the entity autocomplete endpoint (/v1/suggest/entities) and reuse the identifier it returns.

How do I measure whether coverage is positive or negative?#

Reputation is about the tone aimed at you, not the average mood of the article. That is what entity.sentiment.polarity gives you: paired with organization.name or brand.name, it keeps only articles where the sentiment measured toward your specific brand matches positive, negative, or neutral. To size the split, run the same filters through /v1/news/count twice — once for each polarity — and compare the two counts.

curl "https://api.apitube.io/v1/news/count?organization.name=Tesla&entity.sentiment.polarity=positive&published_at.start=NOW-7DAYS&api_key=YOUR_API_KEY"

The count endpoint returns { "status": "ok", "count": 128, "request_id": "..." } and costs one request, so a positive-versus-negative comparison for the last week is two cheap calls. In the full article response, every item in the entities array carries its own sentiment block with a score, a polarity, and a mentions breakdown counting positive, neutral, and negative references — the raw signal behind the filter. For a stricter cut, entity.sentiment.score.min and entity.sentiment.score.max (each from -1 to 1) let you keep only strongly-toned coverage and drop the borderline middle.

How do I track mention volume over time?#

To see whether you are being talked about more or less, hold the brand filter fixed and move the date window with published_at.start and published_at.end. Both accept absolute timestamps and relative shortcuts such as NOW-7DAYS, NOW-24HOURS, or NOW-1WEEK. Counting each window with /v1/news/count builds a volume series without downloading a single article.

curl "https://api.apitube.io/v1/news/count?brand.name=Nike&published_at.start=NOW-24HOURS&api_key=YOUR_API_KEY"

For a bucketed view in one call, /v1/news/trends accepts the same brand filter plus field=source.id (or field=entity.id) and time_bucket=day, returning counts grouped per day. Add compare=true with a compare_window such as 7DAYS to get the change versus the previous period. The trends endpoint looks back a maximum of 30 days per request, so use it for recent momentum and the count series for longer stretches.

Which outlets are shaping my reputation?#

Not every mention carries the same weight. To see who is driving your coverage, send your brand filter to /v1/news/trends with field=source.id — the response ranks the outlets publishing about you by article count, so you learn where the conversation is concentrated. To focus on authoritative publishers, add source.rank.opr.min to require a minimum Open Page Rank, or is_verified_source=1 to keep only higher-ranked, non-duplicate sources. When you already know the outlet, source.domain narrows any query to a single publisher.

curl "https://api.apitube.io/v1/news/trends?field=source.id&organization.name=Tesla&is_verified_source=1&api_key=YOUR_API_KEY"

How do I get alerted to new coverage instantly?#

Re-running a search on a timer wastes requests and adds lag. The /v1/news/stream endpoint accepts the exact same brand and sentiment filters and pushes each new matching article over Server-Sent Events (SSE) shortly after it is indexed, sending only articles newer than the ones you have already seen. That turns your reputation watch into a live feed instead of a poll.

curl -N -H "X-API-Key: YOUR_API_KEY" \
  "https://api.apitube.io/v1/news/stream?organization.name=Tesla&language.code=en"

For a hands-off alert that calls your own server, set up a webhook on a saved search from the dashboard — webhooks are created in the dashboard, not through an API call. Pair the stream with entity.sentiment.polarity=negative when you want the fastest possible warning on a reputation risk, as covered in detect negative mentions quickly.

Common Questions#

• Why use entity sentiment instead of overall sentiment?
• How do I monitor several brands at once?
• Does counting or trends download the article bodies?

Why use entity sentiment instead of overall sentiment?#

sentiment.overall.polarity scores the tone of the whole article, so a piece that mentions ten companies can read as “neutral” while still being harsh about you. entity.sentiment.polarity scores the tone toward your brand specifically, which is what reputation work needs. The entity-level sentiment guide breaks down the difference and the mentions counts in full.

How do I monitor several brands at once?#

Entity name filters such as organization.name and brand.name accept up to three comma-separated values per request, and entity.id accepts up to three IDs. Put your brand and its sub-brands in one call, then reuse that same filter set across /v1/news/count, /v1/news/trends, and /v1/news/stream so every view of your reputation stays aligned.

Does counting or trends download the article bodies?#

No. /v1/news/count returns only a number, and /v1/news/trends returns aggregated counts per source or entity — neither returns article bodies. Each costs one request, which makes them the cheap way to measure volume and momentum before you spend a heavier call fetching the actual coverage from /v1/news/everything.