Sofascore Scraper — Live Scores, Events & Results | $1.9/1K

Sofascore Scraper — Live Scores, Events & Results

Extract live scores, scheduled fixtures and results from Sofascore for 18+ sports — football, basketball, tennis, baseball, hockey, and more.

Ideal for live odds models, sports data feeds, betting analytics pipelines, and match-tracking applications.

---

Use cases

• Live odds & in-play betting models — poll live scores and match minute in real-time
• Sports data feeds — collect daily fixture/result data across dozens of leagues
• Betting analytics — compare pre-match schedules vs. final results
• Fantasy sports automation — track scores and status across multiple events
• Research & journalism — pull historical results or monitor ongoing tournaments

---

What you get

Field	Description
home_team / away_team	Full team names
home_score / away_score	Current scores (null = not yet played)
home_score_period1/2	Period-level breakdown (halves, quarters, sets)
status	scheduled / live / finished / postponed / cancelled
status_description	Sofascore label: 1st half, Halftime, 2nd half, etc.
live_minute	In-game minute for live events
start_time	ISO-8601 UTC kickoff time
tournament / league / country	Competition hierarchy
round / round_name	Round number + name
event_id / event_url	Sofascore IDs and direct link
parse_confidence	Data quality: 1.0 = full API data

---

Sample output

{
  "event_id": "16092698",
  "event_url": "https://www.sofascore.com/japan-south-africa/VsaMsas#id:16092698",
  "sport": "football",
  "country": "World",
  "tournament": "International Friendly Games, Women",
  "league": "International Friendly Games, Women",
  "tournament_id": "1361",
  "round": null,
  "round_name": "",
  "home_team": "Japan",
  "away_team": "South Africa",
  "home_team_id": "5781",
  "away_team_id": "38024",
  "home_score": 0,
  "away_score": 1,
  "home_score_period1": 0,
  "away_score_period1": 1,
  "home_score_period2": 0,
  "away_score_period2": 0,
  "status": "live",
  "status_code": 8,
  "status_description": "2nd half",
  "live_minute": 72,
  "start_time": "2026-06-09T08:00:00+00:00",
  "start_timestamp": 1749456000,
  "scraped_at": "2026-06-09T10:31:00+00:00",
  "parse_confidence": 1.0
}

---

Input

Field	Type	Default	Description
sport	select	football	Sport slug: football, basketball, tennis, baseball, hockey…
mode	select	by-date	by-date = all events on a given date; live = in-play events only
date	string	today UTC	Date filter YYYY-MM-DD. Only used in by-date mode.
statusFilter	select	all	Filter by scheduled, live, finished, or all
maxItems	integer	100	Maximum records to return (0 = unlimited)
proxyConfiguration	proxy	RESIDENTIAL	Apify RESIDENTIAL proxy (billed to your run)

Tip: by-date mode is the most reliable — it returns events regardless of time of day and is the best choice for scheduled pipelines.

---

Supported sports

Football/Soccer, Basketball, Tennis, Baseball, Ice Hockey, Volleyball, Handball, American Football, Rugby, Cricket, Badminton, Table Tennis, Cycling, Golf, MMA, Boxing, Snooker, Darts

---

Technical notes

• Transport: the actor reads Sofascore's web JSON endpoints through Apify Residential proxy first, then falls back to a resilient browser only if the JSON path is unavailable. No buyer API key, no buyer proxy account required.
• Access: handled server-side with Apify proxy and browser fallback, so runs stay reliable without setup on your side.
• Reliability: popular matches are additionally enriched from the page's embedded data (team ids, exact kick-off timestamp, round) for a fuller record; live scores and status always reflect the real-time page.
• Live fallback: when live mode finds 0 in-play events (off-peak hours), the actor automatically returns today's full schedule.
• Pricing: pay per event item returned.

💰 Pricing & how we compare

Pay-per-result (PPE): $0.99 / 1K results. You are billed per event-item actually returned — plus the tiny apify-actor-start fee Apify waives for short runs. No subscription, no API key, no proxy fee on top.

Our edge: Cheapest credible PAID Sofascore source · live + scheduled by sport & date · 15+ sports · no API key.

Pricing examples (pay only for what you get, minus Apify's 20%):

Volume	Cost
100 results	$0.10
1,000 results	$0.99
10,000 results	$9.90

How rivals price the same job (live Apify Store, checked 2026-06-09)

Actor	Their price	What they lack vs us
parseforge/sofascore-live-scraper	$33.50/1K	100% success but ~34× our price per result
maximedupre/sofascore-live-events-scraper	$30.15/1K	~30× our price
azzouzana/sofascore-scraper-pro	FREE	569 users, but free tier = no support guarantee, URL-only input

Prices above are competitors' live Store prices at the time of writing; ours is set to sit just below the strongest comparable while returning richer, quality-scored data.

🤖 Use with AI agents (MCP)

This actor is agent-ready (category MCP_SERVERS). Point any MCP client (Claude Desktop, Cursor, n8n AI, LangGraph) at it:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?actors=bovi/sofascore-live-events",
      "headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }
    }
  }
}

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Ticketmaster Radar

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.