Skip to main content

1. Overview

The Industry News Monitoring API fetches the latest news articles for a given industry topic or sector, enriched with AI-generated summaries, geographic signals, and source metadata. Results are returned synchronously in the HTTP response — no job polling required. This is a synchronous GET API — you pass a free-text topic and optional filters as URL parameters, and receive a paginated array of enriched news articles immediately. Unlike the Company News Monitoring API, which fetches news anchored to a specific company, this API accepts any natural-language topic — a sector, a technology, a theme, a geopolitical event, or a cross-company trend. The breadth of coverage is defined by the topic string and optionally narrowed by geo and date range. Each article in the response includes:
  • AI summary — a concise, machine-generated synopsis of the article’s key facts and implications
  • Geographic tags — ISO 3166-1 alpha-3 country codes identifying which geographies are relevant to the article
  • Publisher and source metadata — article URL, title, publication datetime, and source attribution
  • Article identifier — a stable numeric id for deduplication across paginated requests
Common use cases:
  • Sector monitoring for investment research — Track news on themes like “warehouse automation”, “GLP-1 drugs”, or “offshore wind” across a rolling 30-day window without being tied to a specific company
  • Geopolitical and macro intelligence — Monitor topics like “US-China trade war”, “European energy security”, or “emerging market debt” filtered to specific regions using the geo parameter
  • LP and fund reporting — Aggregate industry-level developments across portfolio sectors for quarterly reporting or LP briefings
  • Market entry and expansion research — Filter a topic to a specific country or region (e.g., “electric vehicle charging” in IND) to surface market-specific activity
  • Thematic investment screening — Use the ai_summary field to efficiently triage large volumes of sector news before reading full articles
  • Regulatory and policy tracking — Monitor topics like “data privacy regulation”, “carbon border adjustment”, or “AI legislation” with geographic narrowing to track jurisdiction-specific developments
This API is synchronous. Results are returned directly in the HTTP response — no job submission or polling required. See How Sync APIs work.

2. Quick Start

Step 1 — Make a simple request
Step 2 — Narrow by geography and date range
Step 3 — Work with the articles

3. Authentication

All requests must include a Bearer token in the Authorization HTTP header. No other authentication method is supported.
API tokens are issued from your Wokelo account. Navigate to Account Details → API Credentials in the Wokelo dashboard to get your client id and client secret. Contact support@wokelo.ai if you do not yet have API access.
Never expose your token in client-side code, browser requests, or public repositories. A missing or invalid token returns 401 Unauthorized. A valid token without sufficient plan permissions returns 403 Forbidden.

4. Request Reference

Endpoint
All parameters are passed as URL query parameters. Full request example:

5. Response

Response structure

Article object fields

Each object in the data array contains the following fields: Article identity AI enrichment Source and geography
The Industry News Monitoring API returns a leaner article object than the Company News Monitoring API. Fields like sentiment, primary_tag, secondary_tags, newsworthiness_impact, company_names, publisher, author, and scraped_text are not included in industry news responses. Use ai_summary for content triage and url to fetch the full article when needed.

Notes on the geo field

The geo array reflects countries that are mentioned or relevant in the article — not necessarily where the article was published. A single article covering US-China trade policy may have ["USA", "CHN"]. An article about a regional development project may have only one code.
  • Multi-country articles — articles covering diplomatic events, bilateral trade deals, or multinational company activity commonly list three or more country codes
  • Empty geo — some articles have an empty geo array when country detection was inconclusive; these are still returned unless you have filtered by geo
  • geo filter behaviour — when you pass geo=IND,SGP, the API returns articles tagged with IND or SGP, not exclusively articles tagged with both

Pagination notes

Industry topic queries can return very large result sets. For broad topics like “trade war” or “artificial intelligence” the total count can exceed several thousand. Always check total against count and paginate using offset until all records have been retrieved. The recommended approach is to stop when count returns 0 or len(all_articles) >= total.

6. Examples

Monitoring a sector in a specific region

Fetch all real estate development news in the UAE for a specific month — useful for generating a sector brief or LP update.
Sample response (excerpt):

Multi-region sector sweep

Monitor a technology sector across several markets simultaneously by passing multiple geo codes. Useful for tracking a theme across different regulatory or market environments.

Rolling 30-day monitoring pipeline

Set up a recurring pull that always covers the most recent 30 days, suitable for a weekly digest or automated feed.

Paginating through large topic result sets

For broad topics, total can significantly exceed limit. Paginate using offset until all records are retrieved.

Comparing sector activity across geographies

Pull the same topic for multiple regions and compare article volume and recency — useful for understanding where in the world a theme is most actively developing.

JavaScript / Node.js


7. Error Handling

The API uses standard HTTP status codes. All error responses include a JSON body with a detail or message field. Error response example:
Retry logic with exponential back-off:

8. Best Practices

Write a specific, descriptive topic — this is the single highest-impact parameter The topic field drives the entire article retrieval. A vague topic like "technology" returns an enormous, noisy result set. A specific topic describing the exact theme, technology, or event produces a tight, actionable feed:
Use geo to narrow scope, not to replace topic specificity The geo filter restricts articles to those tagged with specific countries, but a vague topic with aggressive geo filtering can still return a noisy result set. Lead with a specific topic and use geo to reduce geographic noise:
Use ISO 3166-1 alpha-3 codes — not alpha-2 The geo parameter requires 3-letter codes ("USA", "GBR", "DEU") not the 2-letter equivalents ("US", "GB", "DE"). Passing alpha-2 codes will not filter correctly and may return unexpected results.
Set a date window for every production run Without start_date and end_date, the query returns articles across the full Wokelo index, which for active topics can mean thousands of articles. Always bound queries to the window you intend to process — 30-day windows work well for regular monitoring runs, 7-day windows for weekly digests:
Use article id for deduplication across runs The id field is a stable identifier for each article in Wokelo’s index. When running the same topic query on an overlapping date range (e.g. daily refreshes), deduplicate by id to avoid processing the same article twice:
Blacklist press release aggregators to improve signal quality Wire services and press release aggregators (prnewswire.com, businesswire.com, globenewswire.com) publish high volumes of company-issued releases that can dominate topic results. Blacklisting these domains surfaces editorial journalism and independent analysis:
Use ai_summary for fast triage before fetching full articles The ai_summary field provides a reliable 2–4 sentence synopsis that is sufficient for most triage decisions. Read full articles via the url field only for items that pass your relevance threshold, rather than attempting to scrape all articles in a result set. Understand the difference from Company News Monitoring The Industry API response schema is intentionally leaner — it does not include sentiment, primary_tag, secondary_tags, newsworthiness_impact, company_names, publisher, author, or scraped_text. If you need these enrichment fields, or if your monitoring is anchored to specific companies, use the Company News Monitoring API instead. The two APIs are complementary: industry monitoring for broad thematic coverage, company monitoring for entity-level depth.

Company News Monitoring

Fetch company-specific news with richer enrichment — sentiment, event categories, company mentions, and full article text.

Newsfeed

Retrieve a curated, cross-company newsfeed based on a topic, theme, or portfolio watchlist.

Industry Deep Intelligence

Generate a comprehensive AI research report on any industry — market size, competitive dynamics, key players, and outlook.

Industry Research

Run a structured, async AI research workflow on an industry topic and receive a formatted output report.

Market Map

Discover and map all companies competing in a specific market or product category.

Supporting APIs

Company Search, Request Status, and other utilities used alongside monitoring workflows.