What the API does and who it is for
Real-Time News Data, built by OpenWeb Ninja, acts as a structured interface to Google News — one of the broadest aggregators of online journalism. Rather than scraping news sites directly or managing RSS feeds, developers can make a single HTTP GET request and receive article data organised by topic, geography, publication, or keyword.
The API targets a wide audience: newsroom tools, media monitoring dashboards, research platforms, content aggregators, alert systems, and any application that needs a continuously fresh feed of articles without the operational overhead of crawling the web. Because the underlying data source is Google News, coverage is global and multilingual, which matters for teams building products that serve audiences in multiple countries.
Endpoint walkthrough
The API exposes seven GET endpoints, each addressing a distinct news retrieval pattern.
/search
The search endpoint lets you retrieve articles matching a query string. An optional time-range parameter lets you narrow results to a specific window — useful for news monitoring workflows where you want only articles published in the last hour or day, or for historical research bounded by a date window.
/top-headlines
Returns the current top stories for a given country. This is the most straightforward endpoint for anyone building a general-purpose news feed that needs to reflect what is trending in a specific national context.
/topic-headlines
Allows you to fetch headlines for a broad topic category (for example, World, Sports, or Technology) or for a named publication such as CNN or BBC. The dual mode — topic OR publication — gives you flexibility: you can power both a vertical feed and a "follow this source" feature from the same endpoint.
/topic-news-by-section
Goes one level deeper than /topic-headlines by exposing sections within a topic or publication. If a topic has subsections (say, a technology topic broken into AI, gadgets, and security), this endpoint lets you access those more granular feeds directly.
/local-headlines
Delivers geo-targeted headlines. This is particularly valuable for hyperlocal applications — community news aggregators, real-estate platforms that surface neighbourhood news, or travel apps that want to show what is happening near a user's location.
/full-story-coverage
This is the most distinctive endpoint in the set. Given a story, it returns not just the lead article but the broader coverage: sub-articles, related top news, and posts from X (formerly Twitter). For media intelligence tools or journalist research dashboards, this endpoint collapses what would otherwise be several separate queries into one.
/language-list
A utility endpoint that returns the valid languages supported for a given country code. You should call this before building any UI that lets users select their preferred language, to avoid passing unsupported values to the other endpoints.
Reliability and performance
The API records a 99% average success rate, which is a solid figure for a data product that relies on an external source like Google News. The average latency sits at 2,038 ms. That is on the higher end for a web API, so it is worth factoring into your architecture: for anything user-facing in a synchronous request path, consider calling this API asynchronously or caching responses on your side. For background jobs, scheduled polling, and server-side rendering with appropriate timeouts, the latency is unlikely to be a blocker.
Pricing breakdown
Real-Time News Data uses a freemium model with four tiers.
| Plan | Monthly price | Requests included | Overage per request | Rate limit |
|---|---|---|---|---|
| BASIC | $0 | 100 | — | 1 req/sec |
| PRO (recommended) | $25 | 10,000 | $0.0030 | 10 req/sec |
| ULTRA | $75 | 50,000 | $0.0020 | 20 req/sec |
| MEGA | $150 | 200,000 | $0.0010 | 30 req/sec |
The free BASIC tier is genuinely limited at 100 requests per month and a cap of one request per second. That ceiling is fine for evaluating the API, testing endpoint shapes in development, or running a very low-traffic personal project — but it will be exhausted quickly in any production context. A moderately active news widget that refreshes every few minutes for a handful of concurrent users could burn through the free quota in days.
The PRO plan at $25/month with 10,000 requests is a reasonable entry point for most production workloads. If you cache aggressively — storing top-headlines responses for several minutes before re-fetching — 10,000 monthly requests can support a surprisingly busy application. Overage on PRO is $0.003 per request, so a burst of 5,000 extra calls in a month would add $15.
ULTRA and MEGA make sense for continuous monitoring systems, large aggregators, or multi-tenant SaaS products where many customers each generate their own queries. The overage rates drop to $0.002 and $0.001 respectively as you scale, which is worth modelling before committing to a plan if your usage is spiky rather than steady.
For teams with very high volumes, OpenWeb Ninja also offers a separate Real-Time News Data (Mega) API and custom plan options via their support channels.
Practical use cases
News aggregator or reader app — Combine /top-headlines (for the front page) with /topic-headlines (for vertical sections) and /search (for a user query bar). The /language-list endpoint helps you present language options correctly per country.
Media monitoring and brand alerts — Poll /search on a schedule with brand or keyword queries and a short time range filter to detect new coverage as it appears. The full-story endpoint can then expand any hit into its broader narrative.
Research and journalism tools — /full-story-coverage is well-suited to journalists who need to understand the complete landscape around a breaking story, including the social conversation on X, without manually aggregating from multiple tabs.
Hyperlocal features — /local-headlines lets you embed neighbourhood or city news into location-aware apps without building a separate news pipeline.
Limitations and things to check before integrating
Latency at ~2 seconds means synchronous, user-triggered fetches will feel slow unless you cache on your server or pre-fetch in the background. Plan your architecture accordingly from the start.
Google News as the underlying source implies that the API's data availability and freshness are tied to what Google News indexes. Niche or very local publications that Google does not index well will be underrepresented.
The free tier caps out at 100 requests per month, so don't plan a production launch on the BASIC plan without a clear path to upgrading.
Rate limits increase with tier, from 1 req/sec on BASIC to 30 req/sec on MEGA. If you need to run parallel bulk queries, the lower tiers will serialize your requests significantly.
No mention of webhook or streaming delivery — the API is a pull model only, so if you need push-style alerts you will need to implement polling on your end.
Getting started
The API is listed on RapidAPI and hosted by OpenWeb Ninja. Sign up for the BASIC plan to get an API key and explore the endpoint schemas at no cost. Start with /language-list to understand the locale parameters, then try /top-headlines with a country code to verify the response structure. Once you have a feel for the data shape and the latency characteristics in your environment, you can size a plan based on your anticipated monthly request volume.
For integration assistance, OpenWeb Ninja offers support via email at [email protected] and a live Discord community. Custom or enterprise-volume plans are negotiated directly with their team.
