How to monitor corporate and supplier risk#

To monitor corporate and supplier risk, query /v1/news/everything, pin each supplier with organization.name (or its numeric entity.id), and keep only the coverage that signals trouble with event.type — codes like bankruptcy, lawsuit, recall and layoffs. There is no separate “risk” endpoint: you assemble a risk feed from the shared filter chain, then point the same filters at the /v1/news/stream SSE feed or a dashboard webhook to get alerted the moment a supplier hits the news.

curl "https://api.apitube.io/v1/news/everything?organization.name=Boeing&event.category=business&published_at.start=NOW-1WEEK" \
  -H "X-API-Key: YOUR_API_KEY"

You can pass the key as the api_key query parameter or as an X-API-Key header. This request returns business-event coverage of one supplier from the last seven days, newest first (results sort by published_at descending by default).

How do you watch a portfolio of suppliers?#

Track suppliers by entity, not by loose keywords, so a company name never collides with an unrelated word. Pin one vendor with organization.name, which resolves the name to a tracked organization and matches every article that mentions it. You can pass up to three comma-separated names, combined with OR logic, so one request covers a small supplier portfolio:

curl "https://api.apitube.io/v1/news/everything?organization.name=Boeing,Airbus,Rolls-Royce" \
  -H "X-API-Key: YOUR_API_KEY"

Each name must be 1–120 characters. If a name does not resolve, the request stops with a not found error — look the vendor up with entity autocomplete and switch to the stable numeric entity.id instead, which does not depend on exact spelling:

curl "https://api.apitube.io/v1/suggest/entities?prefix=Boeing" -H "X-API-Key: YOUR_API_KEY"
# take the numeric "id" from a result:
curl "https://api.apitube.io/v1/news/everything?entity.id=12345" -H "X-API-Key: YOUR_API_KEY"

entity.id also accepts up to three comma-separated ids with OR logic. To silence a noisy vendor without dropping the rest, exclude it with ignore.organization.name. See how to find news mentioning a person or company for the full entity rules.

How do you catch corporate risk events?#

A supplier appearing in the news is not automatically bad news. Narrow to the events that actually signal risk with event.type, which matches the primary business event the pipeline tagged on each article. Risk-relevant business codes include bankruptcy, layoffs, lawsuit, recall, data-breach, regulatory-action, closure, stock-movement and executive-change. You can pass up to five codes, combined with OR:

curl "https://api.apitube.io/v1/news/everything?organization.name=Boeing&event.type=lawsuit,recall,regulatory-action" \
  -H "X-API-Key: YOUR_API_KEY"

To cast a wider net over every business event at once, use event.category=business instead of listing codes (the other categories are society and environment). An unknown event code stops the request with an HTTP 400 error, so pull the exact list of valid codes from /v1/news/event-types first, and remove event types you don’t care about with ignore.event.type. See how to filter news by event type and category for the full event rules.

How do you surface only negative coverage about a supplier?#

Bad news is negative news. Once a supplier is pinned, add entity.sentiment.polarity=negative to score the tone toward that supplier specifically, separate from the rest of the article — so you catch a negative mention of one vendor even inside an otherwise upbeat industry piece:

curl "https://api.apitube.io/v1/news/everything?organization.name=Boeing&entity.sentiment.polarity=negative" \
  -H "X-API-Key: YOUR_API_KEY"

entity.sentiment.polarity accepts positive, negative or neutral. For a sharper cut, bound the entity’s sentiment score (a −1 to 1 band) with entity.sentiment.score.min and entity.sentiment.score.max — for example entity.sentiment.score.max=-0.3 keeps only clearly negative mentions. This is different from sentiment.overall.polarity, which scores the tone of the whole article rather than the supplier’s slice of it.

How do you keep the feed recent and urgent?#

A risk desk wants the newest and most urgent items first. Bound the window with published_at.start, which accepts absolute dates (2026-06-01) and relative Solr-style values (NOW-1DAY, NOW-1WEEK, NOW-3MONTHS), and add is_breaking=1 (exactly 0 or 1) to keep only stories flagged as breaking:

curl "https://api.apitube.io/v1/news/everything?event.category=business&is_breaking=1&published_at.start=NOW-1DAY&per_page=250" \
  -H "X-API-Key: YOUR_API_KEY"

per_page defaults to 100 and maxes out at 250; walk deeper with page. On the Free plan, paging stops after the first 5 pages, so use a paid plan for wide sweeps. To watch a whole supplier sector rather than named vendors, swap the entity selector for industry.id (a numeric industry code). To trim each result to just what an alert needs, add fl=id,title,source.domain,published_at.

How do you get supplier-risk alerts in real time?#

Polling everything returns what already exists; real risk monitoring needs push. Keep the exact same filters and open the Server-Sent Events stream at /v1/news/stream — it runs the same filter chain and pushes each new matching article as it is published, polling every 30 seconds with a 30-second heartbeat, and supports the Last-Event-Id header so you can resume without gaps:

curl -N "https://api.apitube.io/v1/news/stream?organization.name=Boeing&event.type=lawsuit,recall,bankruptcy" \
  -H "X-API-Key: YOUR_API_KEY"

Each delivered article counts as one request against your stream quota. If you would rather have APITube POST risk items to your own endpoint (a Slack channel, a GRC tool), create a webhook — that is done in the dashboard, not over the API, and it pushes matching articles to your URL with a signed request. The full parameter list lives in the News API parameters reference.

Common Questions#

• Is there a dedicated corporate-risk endpoint?
• How do I track many suppliers at once?
• Which event types signal corporate risk?
• How do I get alerted the moment a supplier is in trouble?

Is there a dedicated corporate-risk endpoint?#

No. Corporate and supplier risk monitoring uses the same /v1/news/everything endpoint and the same organization.name, entity.id, event.type, entity.sentiment.*, is_breaking and published_at filters as any other subject. You define what counts as risk with those filters — there is no separate risk route.

How do I track many suppliers at once?#

organization.name and entity.id each accept up to three comma-separated values, combined with OR logic, so a single request can cover three vendors. For a larger portfolio, run one request per group of suppliers, or widen to a whole sector with industry.id. Exclude vendors you don’t want with ignore.organization.name.

Which event types signal corporate risk?#

Use the business event codes that map to trouble: bankruptcy, layoffs, lawsuit, recall, data-breach, regulatory-action, closure, stock-movement and executive-change. Pass up to five in event.type (OR logic), or use event.category=business to include every business event. Validate codes against /v1/news/event-types — an unknown code returns an HTTP 400 error.

How do I get alerted the moment a supplier is in trouble?#

Move from polling to push. Open the /v1/news/stream SSE feed with your supplier and event filters to receive new matching articles as they publish, resuming with Last-Event-Id after a drop, or create a webhook in the dashboard so APITube POSTs each risk item to your endpoint. Both carry the same filters you use on search.