Build a 2026 World Cup App: The 10 APIs You Actually Need

If you Google "world cup api" you'll find a hundred articles comparing live-score providers. That's useful but incomplete. A real 2026 World Cup app touches eight distinct API lanes, and the live-score one is just where you start.

Below is the stack I'd build today, with a free and a paid pick in each lane. Most can be combined for under $50/month total if you cache aggressively, or run entirely on free tiers if your project is non-commercial. Skip to the lane you're shipping next; the article assumes you've already decided to build the thing.

A note on what's not here: analytics (use Mixpanel or PostHog), error tracking (Sentry), and hosting (your call). Those are product infrastructure, not 2026-World-Cup-specific.

1. Live scores

The foundational lane. Without reliable scores, none of the rest matters. Two choices.

The free pick is API-FOOTBALL. Single API key, free tier without a credit card, covers the World Cup as a cup competition. The constraint is the free-tier rate limit, which will bite during peak match windows, so cache aggressively or move to paid.

The commercial pick is SportsDataIO Soccer Scores v3. Around $19/month entry, licensed data with an SLA, sub-five-second latency. The bonus is year-round coverage: the same subscription powers Premier League, La Liga, MLS the rest of the year, so you don't have to swap APIs after July.

Detailed comparison and trade-offs in the 2026 World Cup API guide.

2. Match statistics and xG

If your app does post-match recaps, fantasy selection, or any kind of analytical content, you need stats beyond goals and assists. SportsDataIO Soccer Stats v3 is the practical pick, usually bundled with Scores. You get xG (expected goals), shot maps, pass accuracy, key passes, and historical baselines.

There's no good free alternative for proper xG. The free APIs return basic stats only. If you want xG without paying, you're scraping FBref or Understat, which works for a personal project but breaks the moment those sites change their HTML.

3. Host-city weather

Three host countries, 16 cities, outdoor matches in mid-summer. Weather matters for fan experience features (kickoff temperature, rain risk for fans heading to stadiums) and for tactical content (humidity affects player performance, especially in matches in Dallas or Houston).

The free pick is AccuWeather, which has a developer tier that covers current conditions and short-term forecasts. The paid pick if you outgrow it is Visual Crossing Weather or upgrading to AccuWeather's commercial plans. Hit one of these on cron once an hour per host city, cache the result, and you'll never wake up to a quota issue.

4. Maps and venues

Every World Cup app I've seen with poor user reviews has one thing in common: bad maps. "How do I get to MetLife Stadium" is a query users will run, and rolling your own map tile is unrealistic. Use a real maps API.

Mapbox has a free tier generous enough for 50,000 map loads per month, which is plenty for a tournament-window app. The drop-in JavaScript SDK is the fastest path to a working stadium map with directions. Alternatives include TomTom Maps and Amazon Location Service, both paid from the start; pick those only if you have an existing relationship with the vendor.

5. Translation

Forty-eight teams. Twenty-plus official languages. Player names with diacritics, country names that have multiple romanizations, city names that change spelling depending on whether you're writing English or Spanish or German. A typeahead that doesn't match "Türkiye" to "Turkey" looks broken.

Google Cloud Translation is the easy pick — the free tier (500K characters/month for new projects) handles entity normalization for a single-language app. If your app is multi-lingual UI, you'll need more, and the per-character pricing is reasonable. Amazon Translate is the AWS-native equivalent and competitive on price; use it if you're already on AWS.

6. Push notifications

The single feature that earns daily-active retention during a tournament: notify users about their team's goals, red cards, full-time results. Build this even if you're a side project.

Amazon SNS is the workhorse. Free tier covers a million publishes per month, which is far more than a personal app will use. It fans out to iOS APNs, Android FCM, SMS, email, and HTTPS webhooks from one publish call, so you don't have to integrate each platform separately.

Practical advice: design your push topics narrow. Don't subscribe a thousand users to a single "all World Cup events" channel. Use topics like team:argentina:goal and team:argentina:red-card and let users opt into the noise level they want. Your bill and your delete-app retention rate will both thank you.

7. News and content

A scoreboard is a starting point, but post-match reactions, pre-match storylines, and breaking news are what bring users back. Five news APIs to pick from.

NewsAPI is the most-asked-about, 150K sources, free Developer tier for non-commercial use. GNews has stronger real-time freshness (Google News-backed) and a much more affordable commercial plan ($50/month vs NewsAPI's $449). MediaStack wins on entry-level pricing ($9.99/month) but the free tier is monthly-capped at 100 calls, which is restrictive. TheNewsAPI is a clean Stripe-style API with low commercial entry ($19/month). Currents API stands out for multi-language coverage with built-in category and emotion metadata, particularly strong on Arabic and Indonesian where NewsAPI is thin.

The practical setup: pick one (GNews if you want commercial flexibility cheaply, NewsAPI if you don't need commercial yet), cache aggressively, surface the source URLs not the article bodies. Most of these APIs return summaries only — you don't want to be in the business of rewriting other people's journalism.

8. Ticketing

Many World Cup apps skip ticketing entirely. That's a missed feature. Fans who use your app for scores are the same fans who might buy tickets through a referral link, and ticketing referral programs are how a free fan app generates revenue without being annoying.

Ticketmaster Discovery API is the primary source. Ticketmaster is FIFA's official US venue ticketing partner, so most of the 78 US matches go through it. Free tier of 5,000 requests/day is generous. The API gives you events, venues, attractions, and price ranges; the affiliate program pays you for referring buyers.

SeatGeek Platform covers the secondary market. They aggregate StubHub, Vivid Seats, and others, with their proprietary Deal Score telling users when a ticket is a value pick. Use both: Ticketmaster for first-party availability, SeatGeek for the "is this ticket a fair price" layer.

Putting it together: a realistic free stack

If your goal is "ship a working 2026 World Cup fan app this weekend without spending money," here's what plugs together:

API-FOOTBALL for scores. AccuWeather for host-city forecasts. Mapbox for the stadium map screen. Google Cloud Translation for the typeahead-entity-fix problem. Amazon SNS for goal push. GNews for the news tab. Ticketmaster Discovery for the ticket affiliate link.

Seven APIs, all on free tiers, all with reasonable docs. Cache everything you can. Avoid putting any free-tier key directly in a mobile client unless you've thought hard about rotation.

When to upgrade

The point you trade up to paid is when one of three things happens. You start paying for hosting because your app has actual users; the same moment, upgrade your scores API to SportsDataIO so a bad day at api-football.com doesn't kill your weekend. You hit a rate-limit wall on news; that's GNews's Essential plan at $50/month. You launch a paid feature like fantasy or transfer evaluation; that's when SportsDataIO Soccer Stats earns its keep.

Most apps don't reach all three. Most apps stay in the "ship something good, then iterate" zone, which the free stack covers. Worry about scaling when you have something worth scaling.

What I'd actually do

If I had a weekend and wanted to ship a World Cup app, the order would be: scores first, then push, then news. Those three create the daily-return habit. Maps, weather, and translation are improvements once the core works. Ticketing comes last because it's a monetization layer, not a user-acquisition layer.

For deeper picks on each lane, the 3-API scores comparison covers the commercial vs free choice in more detail. Everything else is here.