News API Rate Limits Compared: Who Gives You the Most Requests

A news API rate limit is the cap a provider enforces on how many requests (or articles) you can make per minute, day, or month before the API either throttles, errors, or bills overage. Rate limits determine whether a traffic spike is a non-event or a pager incident — and in 2026, no single page compares them across providers. Below is the cross-vendor table, the effective-throughput math (rpm × articles per request), the operational impact of each throttle type, and a decision framework based on how many articles per minute your pipeline actually needs.

This article is for developers sizing capacity for a news data pipeline. All limits verified against public vendor documentation as of 2026-04-16.

Disclosure

APITube is my company. It appears in every table at the same granularity as NewsAPI.org, GNews, Mediastack, and NewsCatcher.

TL;DR

The vendor with the highest headline rpm doesn't always deliver the most articles per minute. Unlike vendors that only publish requests-per-day, APITube and NewsAPI.org expose monthly budgets that allow burst patterns — which means the metric that matters is effective articles per minute (rpm × articles per request), not rpm alone. At the mid-tier commercial level, APITube Corporate delivers the highest effective throughput at 200 rpm × 500 articles/request = 100,000 articles/minute theoretical. GNews Enterprise delivers 100 articles/request but caps at ~17 rpm sustained, yielding ~1,700 articles/minute. NewsAPI.org doesn't publish an rpm cap — throughput is bounded by monthly quota.

The cross-vendor rate-limit table

Notes: GNews daily caps reset at 00:00 UTC. "Not published" means the vendor's docs don't state an rpm cap — throughput is effectively bounded by the monthly quota. NewsCatcher uses a credit model (1 record = 10 credits) and concurrent-job limits rather than traditional rpm. Mediastack's articles-per-request cap not documented in public specs.

Effective throughput: the number that actually matters

Raw rpm is misleading. A vendor at 50 rpm returning 200 articles per request delivers 10,000 articles/minute. A vendor at 17 rpm returning 100 per request delivers 1,700 articles/minute. The first vendor's headline rpm is lower, but its effective throughput is 6× higher.

Read two columns: effective articles/min (peak burst) and sustained art/min (if you spread the monthly budget evenly across 43,200 minutes). Peak burst matters for real-time alerting; sustained matters for scheduled ingestion.

APITube Corporate's 200 rpm with 500 articles/request gives it the highest burst throughput in this comparison. GNews Enterprise's high sustained throughput comes from a large daily cap (25,000 req/day) but a low articles-per-request ceiling. NewsAPI.org's burst is unknowable from public docs — they don't publish an rpm cap, so throughput is effectively governed by how fast their servers respond, constrained by the monthly 250K-request budget.

What happens when you hit the limit

The operational impact of a rate limit depends on how the vendor enforces it. Three models exist in 2026:

Unlike hard-throttle vendors that stop serving data at the cap, soft-overage and PAYG-fallback vendors keep your pipeline alive during traffic spikes — which means the rate-limit comparison isn't just about throughput, it's about what happens to your product when the numbers go over.

Decision framework: how many articles/minute do you need?

Walk the thresholds:

1. < 100 articles/minute (light polling, daily digests, prototype). GNews Essential or Business fits. APITube Basic also works. Budget $50–$108/month.

2. 100–1,000 articles/minute (real-time alerting, multi-topic sweeps, moderate ingestion). APITube Basic (10K art/min burst) or NewsAPI.org Business (burst-dependent) or GNews Enterprise (1,700 art/min). Budget $99–$449/month.

3. 1,000–10,000 articles/minute (high-throughput pipelines, multi-tenant SaaS, research infrastructure). APITube Corporate (100K art/min burst, 200 rpm) is the only self-serve option at this tier. NewsAPI.org Advanced if you don't need explicit rpm guarantees. Budget $199–$1,749/month.

4. > 10,000 articles/minute sustained (enterprise data lake, financial news feed). Custom/Enterprise conversations with any vendor. No published self-serve tier covers this at scale without a sales call.

Match your actual peak requirement to the burst column, and your steady-state to the sustained column. If your traffic is spiky (news breaks → 10× normal volume → baseline), prioritise burst headroom and soft-throttle/PAYG vendors.

FAQ

What are typical news API rate limits?

Typical news API rate limits in 2026 range from 100 requests/day on free tiers to 300,000 requests/month on the highest published self-serve plans. Requests-per-minute caps, where published, range from 10 rpm (APITube's free tier) to 200 rpm (APITube Corporate). Many vendors don't publish explicit rpm limits, binding throughput only via daily or monthly quotas.

Which news API has the highest rate limit?

The news API with the highest published rate limit in 2026 is APITube Corporate at 200 requests/minute and 300,000 requests/month, delivering up to 100,000 articles/minute at 500 articles per request. For monthly volume without an rpm cap, NewsAPI.org Advanced allows 2,000,000 requests/month. For daily volume, GNews Enterprise allows 25,000 requests/day.

Do news APIs throttle or bill overage?

It depends on the vendor. GNews and Mediastack hard-throttle (HTTP 403) at the daily or monthly cap. NewsAPI.org bills overage at $0.0018–$0.0009 per extra request. APITube errors at the monthly cap but offers a PAYG fallback at $0.01/request if pre-funded. The throttle model matters more for operational reliability than the headline limit itself.

What happens when I hit a news API rate limit?

On hard-throttle vendors (GNews, Mediastack), you receive HTTP 403 and no data until the cap resets. On soft-overage vendors (NewsAPI.org), requests continue and the excess appears on your next invoice. On PAYG-fallback vendors (APITube), requests error unless you have a PAYG balance, in which case they continue at $0.01/request. Design your error-handling path based on your vendor's model.

Is there an unlimited news API?

No news API in 2026 offers truly unlimited requests at a published self-serve price. Enterprise tiers from all vendors advertise "unlimited" or "custom" quotas, but these require a sales conversation and a custom contract. The closest self-serve equivalent is APITube's PAYG at $0.01/request with no monthly cap — effectively unlimited at a known per-request cost, bounded only by your balance.

Verdict

The news API rate limit comparison that matters isn't rpm alone — it's effective articles/minute (rpm × articles/request), combined with what happens when you hit the cap. For most mid-volume dev workloads, the choice comes down to GNews's generous daily caps with hard-403 risk, NewsAPI.org's monthly budgets with soft-overage billing, or APITube's explicit rpm guarantees with PAYG fallback.

Size your pipeline against the throughput table, not the pricing page. Try APITube free → apitube.io — 1,000 requests per day at 200 articles/request is enough to validate the burst pattern against your actual query shape.

Resources

• APITube — apitube.io — try it free, sentiment and entities included on every article
• Documentation — docs.apitube.io — endpoints, parameters, response structure, integrations
• Pricing — apitube.io/pricing — all tiers
• APITube blog — apitube.io/blog — more guides and comparisons

Related guides:

• News API Pricing 2026: Real $/1K and Hidden Costs
• Best News API for Developers 2026: 9 Compared
• News API Buyer's Guide 2026