Flashscore Scraper — Live Scores, Fixtures & Results

Scrape Flashscore.com live scores, fixtures, and results across 19+ sports including football, tennis, basketball, hockey, handball, volleyball, and more.

What you get

One record per match, with:

Field	Description
match_id	Unique Flashscore match ID
match_url	Full URL to the match page
home_team / away_team	Team names
home_score / away_score	Scores (null = not yet played)
status	scheduled / live / finished / postponed / abandoned
live_minute	Current match minute (live games only)
kickoff_time	ISO-8601 UTC kickoff timestamp
sport	Sport name (football, basketball, etc.)
country	Country / region
league	Competition / league name
league_url	Full URL to the league page
tournament_id	Internal Flashscore tournament ID
round	Competition round

Inputs

Input	Type	Description
sport	Select	Sport to scrape (default: football)
date	String	Filter by date YYYY-MM-DD (UTC) — leave blank for today's feed
leagueFilter	String	Case-insensitive substring to filter league/country
statusFilter	Select	all / scheduled / live / finished
maxItems	Number	Max records to push (default 100, 0 = unlimited)
proxyConfiguration	Proxy	Apify RESIDENTIAL proxy recommended

Sports supported

football, tennis, basketball, hockey, handball, volleyball, baseball, rugby-union, american-football, cricket, badminton, table-tennis, boxing, mma, cycling, golf, rugby-league, ice-hockey, floorball

How it works

Flashscore uses an internal feed API at GET https://www.flashscore.com/x/feed/f_{sportId}_1_1_en_1 with a static x-fsign: SW9D1eZo authentication header (hardcoded in Flashscore's core_2_2302000000.js). The response is a custom ÷/¬-delimited format containing all match data for the current day.

No JavaScript execution, no HTML parsing — pure API call. Apify RESIDENTIAL proxy handles IP-based restrictions.

Pricing

Pay Per Event (PPE): $1.50 per 1,000 match items returned.

Football: 700+ matches per day. Basketball: 50–100. Tennis: 30–60.

Notes

• The Flashscore feed covers the current day's matches (today's schedule). Use date filter to limit results to a specific day.
• Scores are null for scheduled matches; populated for live and finished games.
• Live games include live_minute (current minute).
• Postponed/abandoned matches have status: postponed or status: abandoned with home_score: null.

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.