Documentation Index
Fetch the complete documentation index at: https://docs.wokelo.ai/llms.txt
Use this file to discover all available pages before exploring further.
1. Overview
The Newsfeed API fetches the latest news articles across one or more industries, enriched with AI-generated summaries, sentiment signals, newsworthiness ratings, and geographic tags. All filters are applied simultaneously in a single POST request body — no chaining of separate calls required. This is a synchronous POST API — you submit a JSON body with your filter combination and receive a paginated array of enriched news articles immediately. The Newsfeed API is the most composable of the three monitoring APIs. Unlike Company News Monitoring (anchored to a specific company) or Industry News Monitoring (driven by a free-text topic query), the Newsfeed API uses a structured taxonomy of pre-defined industry names and event categories as filters. This makes it well-suited to building consistent, reproducible news pipelines that need to run reliably across many industry verticals simultaneously. What makes this API distinct:- Multi-industry in one request — pass an array of industries (e.g.
["Financial Services & Fintech", "Enterprise Software & Cloud"]) to get a unified feed across sectors in a single call - Sentiment filtering at query time — filter to only
"positive","negative", or"neutral"articles before results are returned, rather than filtering client-side after fetching everything - Breaking news flag — set
breaking_news: trueto retrieve only articles Wokelo has classified as high-velocity, high-importance breaking developments - Event category filtering — combine industry filters with event category filters (e.g.
"Mergers & Acquisitions","Product Launches & Enhancements") from the same 86-category taxonomy used by the Company News API - Geo as array — pass multiple countries as an array rather than a comma-separated string
- AI summary — a concise, machine-generated synopsis of the article’s key facts
- Sentiment —
Positive,Neutral, orNegativeclassification at the article level - Newsworthiness impact —
High,Medium, orLowrating - Geographic tags — ISO 3166-1 alpha-3 country codes relevant to the article
- Article identifier — a stable numeric
idfor deduplication
- Morning intelligence briefing — Pull
breaking_news: trueacross your coverage sectors each morning to surface only high-velocity developments worth reading - Positive deal flow signal — Filter
sentiment: "positive"across["Financial Services & Fintech", "Enterprise Software & Cloud"]to surface fundraising, M&A, and partnership activity worth tracking for deal sourcing - Negative signal monitoring — Filter
sentiment: "negative"across portfolio sectors to catch emerging adverse developments — layoffs, regulatory actions, leadership changes — before they become widely covered - Multi-sector LP reporting — Pull a combined news feed across all sectors in your fund’s thesis at the end of each month for structured LP update content
- Regulatory and policy tracking — Combine
category: ["Regulatory & Compliance", "Policy & Legislative Changes"]with specificgeoarrays to track jurisdiction-specific regulatory changes across a sector - Thematic investment screening — Use
industry+category+geotogether to identify investment activity (e.g. M&A and equity fundraising in healthcare in Southeast Asia) at scale
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 request3. Authentication
All requests must include a Bearer token in theAuthorization HTTP header. No other authentication method is supported.
4. Request Reference
Endpoint| Parameter | Type | Required | Description |
|---|---|---|---|
industry | string[] | Optional | Array of industry names from Wokelo’s controlled taxonomy. Pass one or more to restrict the feed to those sectors. View all 28 supported industry names. Example: ["Financial Services & Fintech", "Healthcare & Life Sciences"]. |
category | string[] | Optional | Array of news event categories from Wokelo’s 86-category taxonomy. Restricts results to articles tagged with any of the specified categories. View all supported categories. Example: ["Mergers & Acquisitions", "Product Launches & Enhancements"]. |
sentiment | string | Optional | Filter by article-level sentiment. Accepted values: "positive", "negative", "neutral". Case-insensitive. Omit to return articles of all sentiments. |
breaking_news | boolean | Optional | Set to true to return only articles Wokelo has classified as breaking news. Omit or set to false to return all articles. |
geo | string[] | Optional | Array of ISO 3166-1 alpha-3 country codes. Returns only articles tagged with at least one of the specified countries. Example: ["USA", "GBR", "DEU"]. |
published_date_after | string | Optional | Start of the date window for articles (YYYY-MM-DD). Inclusive. |
published_date_before | string | Optional | End of the date window for articles (YYYY-MM-DD). Inclusive. |
limit | integer | Optional | Maximum number of articles to return. Default 100, max 1000. |
offset | integer | Optional | Number of articles to skip before returning results. Default 0. Use with limit for pagination. |
blacklisted | string[] | Optional | Array of publisher domains to exclude from results. Include the full domain starting with https://. Example: ["https://www.prnewswire.com/", "https://www.businesswire.com/"]. |
All parameters are optional — the API will return all recent articles if no filters are passed. In practice, always supply at least
published_date_after / published_date_before to avoid processing an unbounded backlog.5. Response
Response structure
| Field | Type | Description |
|---|---|---|
status | string | "success" when the request was processed successfully. |
data | array | Array of enriched article objects. |
count | integer | Number of articles returned in this response batch. |
total | integer | Total number of matching articles available across all pages. |
limit | integer | The limit value applied to this response. |
offset | integer | The offset value applied to this response. |
Article object fields
Each object in thedata array contains the following fields:
Article identity
| Field | Type | Description |
|---|---|---|
id | integer | Stable numeric identifier for the article in Wokelo’s index. Use for deduplication across paginated requests or recurring pipeline runs. |
url | string | Canonical URL of the original article. |
title | string | Headline of the article as published. |
published_date | string | Publication datetime in YYYY-MM-DD HH:MM:SS format (UTC). |
| Field | Type | Description |
|---|---|---|
ai_summary | string | AI-generated 2–4 sentence summary of the article’s key facts and implications. |
| Field | Type | Description |
|---|---|---|
sentiment | string | Article-level sentiment: "Positive", "Neutral", or "Negative". Note the response uses title case even when the request filter uses lowercase. |
newsworthiness_impact | string | Strategic significance rating: "High", "Medium", or "Low". |
| Field | Type | Description |
|---|---|---|
source | string | Wokelo’s internal signal source designation. Either "Wokelo" (directly indexed) or "Google" (sourced via search). |
geo | string[] | Array of ISO 3166-1 alpha-3 country codes identifying the geographies covered in the article. Empty array when no country was detected. |
Sentiment values
| Request filter value | Response field value | Meaning |
|---|---|---|
"positive" | "Positive" | Article conveys favourable news — growth, deals, launches, positive outcomes |
"negative" | "Negative" | Article conveys unfavourable news — layoffs, regulatory action, losses, adverse events |
"neutral" | "Neutral" | Factual or mixed coverage with no clear directional bias |
The
sentiment request parameter uses lowercase ("positive", "negative", "neutral"), but the sentiment field in each response article uses title case ("Positive", "Negative", "Neutral"). This inconsistency is expected — normalise to one case in your application logic.Newsworthiness impact values
| Value | Meaning |
|---|---|
"High" | Material development likely to affect strategic positioning, valuations, or stakeholder decisions |
"Medium" | Notable update worth tracking but not immediately actionable |
"Low" | Routine coverage, minor updates, or tangentially related content |
Notes on the Newsfeed response schema vs other monitoring APIs
The Newsfeed article object is intentionally lean. Compared to the Company News Monitoring API, the following fields are not present in Newsfeed responses:primary_tag, secondary_tags, company_names, publisher, author, scraped_text, original_language, company_name. Use ai_summary for content triage and url to access the full article when deeper processing is needed.
6. Examples
Morning breaking news briefing
Pull high-impact breaking news across your coverage sectors each morning — a single call that surfaces only what matters most overnight.Negative signal monitoring across a fund’s portfolio sectors
Monitor for adverse developments — regulatory scrutiny, workforce reductions, financial distress — across all sectors in your investment thesis simultaneously.Positive deal flow feed — fundraising and M&A
Surface equity fundraising, M&A, and partnership activity across target sectors. Useful for identifying deal flow signals and tracking competitive activity.Multi-sector LP update — monthly digest
Aggregate a month’s worth of high-impact news across all fund sectors to feed a structured LP report.Paginating through large result sets
Whentotal exceeds limit, use offset to retrieve all matching articles.
JavaScript / Node.js
7. Error Handling
The API uses standard HTTP status codes. All error responses include a JSON body with adetail or message field.
| Status | Meaning | Cause & Resolution |
|---|---|---|
200 OK | Success | Articles returned successfully. |
400 Bad Request | Invalid parameters | A body parameter has an invalid value — e.g. an unrecognised industry name, an invalid sentiment value, a malformed date, or a non-boolean breaking_news. Check the detail field and verify values against the industry names and news categories taxonomies. |
401 Unauthorized | Auth failed | The Authorization header is missing, malformed, or contains an invalid token. Verify your key in Settings → API Keys. |
403 Forbidden | Insufficient access | Your plan does not include access to this endpoint. Contact support@wokelo.ai to review your plan. |
429 Too Many Requests | Rate limit exceeded | Implement exponential back-off. The response includes a Retry-After header. |
500 Internal Server Error | Server error | Retry after a brief delay. If the issue persists, contact support@wokelo.ai. |
8. Best Practices
Use exact industry names from the taxonomy — partial matches will not work Theindustry parameter requires values that match the controlled taxonomy exactly (e.g. "Financial Services & Fintech", not "Fintech" or "financial services"). Check the full list at /industry-names before constructing your request. Invalid names return a 400 error:
industry and category for precision — each independently reduces noise
Passing only industry returns all event types within a sector, which can produce high-volume, low-signal results for active sectors like healthcare or technology. Adding category filters narrows to the event types you actually care about:
breaking_news: true for daily briefings, omit it for research and backlogs
The breaking_news flag surfaces only articles Wokelo has classified as high-velocity, high-importance developments. It is best used for time-sensitive daily or intraday feeds where you want maximum signal density. For monthly research pulls, historical backlogs, or LP reporting, omit the flag to capture the full range of coverage including analysis pieces and secondary reporting.
Use sentiment to segment feeds by strategic intent
Filtering at request time rather than filtering client-side after fetching reduces payload size and processing time considerably for high-volume sector queries:
published_date_after and published_date_before, the API returns articles across the full Wokelo index. For active multi-industry queries this can mean 10,000+ articles. Always bound queries to the window you intend to process:
blacklisted as an array, not a comma-separated string
Unlike the Company News Monitoring and Industry News Monitoring APIs (which accept blacklisted as a comma-separated URL parameter string), the Newsfeed API takes blacklisted as a JSON array in the request body:
id for deduplication across recurring pipeline runs
When running the same query on overlapping date windows (e.g. daily refreshes with a 7-day window), deduplicate by id to avoid processing the same article more than once:
topic string and matches articles by relevance — giving flexibility for niche or cross-cutting themes. The Newsfeed API uses a structured taxonomy of pre-defined industry names and event categories — giving consistency and reproducibility, but requiring that your topics map to Wokelo’s 28 supported industry buckets. Use Industry News Monitoring for bespoke or narrow topics; use Newsfeed for standardised, recurring pipelines across canonical industry sectors.
9. Related APIs
Company News Monitoring
Fetch company-specific news with the richest enrichment — sentiment, event categories, full article text, and company mention resolution.
Industry News Monitoring
Fetch news on any free-text industry topic — flexible and precise for niche or cross-cutting themes not covered by the standard taxonomy.
Industry Deep Intelligence
Generate a comprehensive AI research report on any industry — market size, competitive dynamics, key players, and outlook.
Target Screening
Identify and score potential acquisition targets — AI-ranked with deal feasibility, synergy, and precedent scores.
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.