A Survey of Public APIs for Building a Football Live Score Site in 2026 — Part 1: News API Review

A football live score site needs more than scores.

The match centre may bring a visitor in, but news gives that visitor a reason to explore a team page before kickoff, return after the final whistle, and follow a competition between matchdays.

This is the first part of a survey of the public APIs needed to build a football live score site in 2026:

1. News APIs
2. Weather APIs for match-day context
3. Football data APIs

Series scope and ground rules

The following rules apply to every article in this series:

1. Candidate source: Every API considered comes from the public-apis repository on GitHub. I chose it because it has more than 400,000 GitHub stars and offers a broad, well-organized set of categories and API options.
2. Review order: APIs are considered in the same order in which they appear in the repository. The order is not a ranking, and providers have not paid for placement.
3. Shortlisting: Every entry in the relevant category is screened, but only APIs that plausibly fit a football live score site receive a detailed review.
4. No implied endorsement: Inclusion in public-apis supplies the candidate pool; it does not mean that the repository or this series recommends an API.
5. Type of review: This is a product-fit and documentation review, not a performance benchmark. Provider claims are identified as documented capabilities rather than independent test results.
6. Snapshot date: Documentation, pricing, and public usage terms were checked on September 5, 2026. They may change, so the linked official pages remain the final source of truth.
7. Meaning of football: In this series, “football” means association football, also called soccer, unless stated otherwise.

Using the same source, order, and rules keeps the selection process consistent across all three parts.

For Part 1, I started with the repository's News section. It currently contains 23 entries, but most are not realistic candidates for this use case. Some are historical archives, RSS readers, single-topic feeds, or APIs for finance, spaceflight, and regional news.

After screening the full list in repository order, I shortlisted seven APIs that could plausibly supply news to football team, competition, or match pages.

What a football news feed actually needs

A generic sports category is useful, but it is not enough. Depending on the country, it may mix association football with American football, basketball, cricket, Formula 1, and other sports.

For a live score site, I would look for:

• Keyword and exact-phrase search for teams, competitions, and players
• Source and domain filters
• Country and language filters
• Publication timestamps in a consistent format
• Enough freshness for pre-match and post-match coverage
• Stable pagination and predictable rate limits
• Clear rights for displaying headlines, summaries, and images
• A realistic path from a prototype to a public website

This last point matters more than the advertised request count. A free plan with 100 requests per day is not useful in production if its license only permits local development.

Shortlist at a glance

API	Free allowance	Free freshness	Free production use	Lowest listed paid plan	Initial fit for a football site
Mediastack	100 requests/month	Free tier is mainly an evaluation tier	Commercial use is listed on paid plans	$24.99/month	Broad coverage, but a very small free quota
Currents	250 requests/day	No artificial plan delay	Metadata and link-out within stated terms; broader republication needs separate rights	$69/month	Strong candidate for a fresh headline feed
GNews	100 requests/day, up to 10 articles per request	12-hour delay	No; development and testing only	€49.99/month	Clean search API for prototypes
News API	100 requests/day	24-hour delay	No; development and testing only	$449/month	Excellent query model, expensive production step
NewsData.io	200 credits/day, up to 10 articles per credit	12-hour delay	Vendor says limited article metadata may be used commercially	$199.99/month	Strong multilingual coverage, but delayed on free
The Guardian	500 requests/day	Current and historical Guardian content	Developer access is non-commercial	Custom quote	Excellent editorial source, but not an aggregator
The News API	100 requests/day, 3 articles per request	Listed as real-time	Not sufficiently clear for me to assume	$19/month	Low paid entry price; clarify rights first

Prices above are the displayed monthly starting prices before taxes, custom licensing, overages, or annual discounts. “Free production use” is deliberately conservative: technical API access does not automatically grant permission to republish third-party articles or images.

1. Mediastack

Mediastack advertises coverage across more than 7,500 sources and 50 countries. Its source directory and country filters are useful for building regional football feeds rather than showing one global stream to everyone.

The current pricing page lists only 100 requests per month on the free plan. The Standard plan begins at $24.99 per month with 10,000 monthly requests and lists historical data and commercial use among its paid capabilities.

One hundred requests per month is enough to inspect the response and build an initial adapter, but not enough to refresh a live website regularly. Even one request every hour would require roughly 720 requests in a 30-day month.

Best fit: Evaluating a broad, conventional REST news feed with a relatively low paid entry point.

Main limitation: The free quota is much too small for an operating news module.

2. Currents

Currents provides latest-news and search endpoints with keyword, category, country, language, date, and source filters. Its current V2 search also supports cursor pagination, which is useful for avoiding unstable page-number traversal as new stories arrive.

The free plan provides 250 requests per day, up to 20 results per request, and up to 30 days of recent history. Currents says newly indexed stories are available to every tier without an artificial plan delay.

For a football site, that is more useful than a large but delayed quota. A job running every ten minutes would consume 144 requests per day, leaving some capacity for team-specific searches.

The important qualification is usage rights. Currents describes self-service access around metadata, attribution, processing, and links to original sources. Republishing articles, retaining a long-term archive, or producing customer-facing derivative content may require separate terms.

Best fit: A prototype or small headline module that links readers to the original publishers.

Main limitation: Do not interpret API access as blanket content syndication rights.

3. GNews

GNews has a compact API with search and top-headline endpoints. Its search syntax supports exact phrases and AND, OR, and NOT, along with filters for language, country, date, and searched fields.

That query syntax is helpful for football. A search for City, United, or Inter by itself will produce noisy results. Boolean expressions make it possible to combine club names with competitions, locations, or known aliases.

The free plan provides 100 requests per day, up to 10 articles per response, 30 days of history, and a 12-hour delay. It is explicitly limited to non-commercial development and testing. Paid production access starts at €49.99 per month and removes the artificial delay.

Best fit: Evaluating search relevance and building a non-commercial prototype.

Main limitation: The free tier cannot power a public commercial live score product.

4. News API

News API has one of the clearest query models in this group. Its /v2/everything endpoint supports phrases, exclusions, Boolean operators, domains, languages, date ranges, and sorting by freshness or relevance. Its top-headlines endpoint also includes a sports category.

The problem is the gap between experimentation and production. The Developer plan provides 100 requests per day, but articles are delayed by 24 hours, CORS is restricted to localhost, and the plan is limited to development and testing. The displayed Business plan starts at $449 per month.

This does not make News API a poor product. It means the free plan is a sandbox, not a launch plan. That distinction is easy to miss when comparing “free API” lists.

Best fit: Testing sophisticated search rules and source selection during development.

Main limitation: A substantial price jump is required before publishing a production integration.

5. NewsData.io

NewsData.io exposes filters for keywords, publishers, countries, languages, categories, and regions. Its documented coverage is especially broad, which makes it interesting for a football product serving leagues and readers outside the English-speaking market.

The vendor's 2026 pricing explanation lists 200 credits per day on the free plan, with up to 10 articles returned per credit. Free results are delayed by 12 hours and do not include full article content.

NewsData.io says the free plan can be used commercially, but that statement comes with an important boundary: its public guidance permits fields such as titles, short descriptions, publisher names, authors, dates, and times, while excluding images and full article content from republication.

That can still work for a football site if the product displays a compact headline card and sends the reader to the publisher.

Best fit: A multilingual football news index where a delay is acceptable.

Main limitation: The free feed is too delayed for breaking team news, and the first paid tier is a large jump.

6. The Guardian Open Platform

The Guardian Open Platform is different from the other candidates because it provides one publisher's journalism rather than aggregating many publishers.

Its Developer access includes up to 500 calls per day, article text, and access to an archive containing more than 1.9 million pieces of content. The Guardian also has a dedicated football section and structured tags, which can produce a more coherent feed than searching an uncurated global index.

Developer access is for non-commercial use. Commercial organizations and developers who want to use Guardian journalism in a product must request commercial access. Attribution and content-use requirements also apply.

Best fit: A high-quality single-publisher football feed or a non-commercial research project.

Main limitation: It cannot provide the breadth of a news aggregator, and commercial use requires an agreement.

7. The News API

The News API offers news search, top stories, source filters, locale filters, language filters, and UTC timestamps. Its free plan requires no billing details.

The pricing page lists 100 requests per day and three articles per request on the free tier. It describes the data as real-time and historical. The Basic plan starts at $19 per month and raises the allowance to 2,500 daily requests with up to 25 articles per request.

There is also a documentation inconsistency worth checking before implementation: the pricing table lists headlines and top stories on the free plan, while the endpoint documentation labels Headlines as available on the Standard plan and above.

On price alone, this is one of the easiest services in the shortlist to move beyond a demo. However, I would ask the provider to confirm both the available endpoints and the intended production and content-display rights before launch. Its public terms are older and use broad non-commercial language, while the product pages describe paid application access. Those ambiguities should not be resolved by assumption.

Best fit: A budget-conscious prototype with a plausible low-cost upgrade path.

Main limitation: Confirm commercial display and redistribution rights in writing.

The candidates I did not shortlist

The public-apis list is a directory, not a pre-filtered product comparison. I excluded several groups:

• Historical archives: Chronicling America and Trove are valuable research collections, but not sources for current football coverage.
• RSS products: Feedbin and The Old Reader solve feed-reading workflows rather than broad news discovery for this use case.
• Single-topic feeds: DataCube AI, Florida Man, Graphs for Coronavirus, MarketAux, and Spaceflight News do not match football.
• Regional or format-specific products: NPR One and Inshorts News are too narrow for a general football site.
• Enterprise or unclear-access candidates: Associated Press may be valuable, but it is not a comparable self-service starting point. I also left out entries whose current documentation or production terms were not clear enough for a fair table.

An API appearing in a public directory should be the beginning of due diligence, not the end.

Query design matters more than the provider name

Football creates unusually ambiguous searches. Consider these club names:

• Manchester City is frequently shortened to City.
• Manchester United may appear as Man United or Man Utd.
• Inter Milan may appear as Inter or Internazionale.
• Paris Saint-Germain may appear as PSG.

A production integration needs a small alias dictionary and query templates. For example:

("Manchester United" OR "Man United" OR "Man Utd")
AND (football OR "Premier League" OR UEFA)

For a match page, include both teams and the competition:

("Arsenal" AND "Liverpool") AND (football OR "Premier League")

Do not rely only on category=sports. Retrieve a slightly broader candidate set, then rank or filter it using known team, competition, player, and venue aliases.

Normalize the response before building the UI

Each provider uses different field names, but the website should depend on one internal shape:

{
  "id": "provider:article-id",
  "title": "Example headline",
  "summary": "Short provider-supplied description",
  "url": "https://publisher.example/article",
  "image_url": null,
  "source_name": "Publisher",
  "published_at": "2026-09-05T12:00:00Z",
  "language": "en",
  "provider": "example"
}

Keeping a provider adapter between the API response and this model makes it possible to change suppliers without rewriting every team and match page.

It also creates one place to implement:

• Canonical URL normalization
• Duplicate-title detection
• Missing-image fallbacks
• UTC timestamp parsing
• Source attribution
• Provider-specific cache rules

A note on article images and full text

An image URL in an API response is not automatically a license to copy or permanently host that image. The same applies to full article content.

For a football live score site, the safest default product is often:

1. Display the headline.
2. Display only the summary or thumbnail allowed by the provider's terms.
3. Credit the publisher.
4. Link directly to the original article.
5. Store only what the applicable agreement permits.

Before launch, review both the API provider's terms and the underlying publisher rights. This is a product requirement, not a detail to postpone until after integration.

Which one would I choose?

There is no honest overall winner without testing live result relevance and confirming the intended license.

Based on the public documentation alone:

• Currents has the most interesting free-tier shape for a fresh, lightweight headline feed.
• NewsData.io is attractive for multilingual discovery and limited commercial metadata use, if a 12-hour delay is acceptable.
• The News API has the lowest displayed paid entry price, but I would clarify its usage rights first.
• GNews has a clean query language for testing football search logic.
• News API offers mature search controls but has the largest visible jump to production pricing.
• The Guardian is the strongest option when editorial consistency matters more than source breadth.
• Mediastack is easy to understand, although its free quota is an evaluation allowance rather than a usable site quota.

My practical shortlist for a prototype would be Currents, GNews, NewsData.io, and The Guardian. Before choosing one for production, I would run the same team-and-competition query set against each candidate, measure freshness and duplicates for at least seven days, and obtain explicit confirmation of the intended display rights.

That live comparison is a separate benchmark. This survey answers the question that comes first: which APIs are credible enough to test?

Next: weather APIs for match-day context

Part 2 will review weather APIs from the same public-apis repository. The goal is not to turn a score site into a weather app. It is to determine whether temperature, rain, wind, and historical match-day conditions can be added reliably without introducing an expensive or fragile dependency.

No news API provider sponsored or reviewed this article before publication.

AI disclosure: AI was used to assist with research organization and English editing. The linked official sources were checked before publication.