OneFootball Scraper - News, Fixtures, Results & Standings
Pricing
from $1.20 / 1,000 result records
Scrape public OneFootball data including football news, upcoming fixtures, match results and league tables. Get clean, structured data for teams, competitions and matches in one place.
Where to collect from: the competitions, teams and news feeds you pick below, or your own OneFootball links.
Only read when mode = search. One entry per competition: the link slug or the full competition link, e.g. premier-league-9, bundesliga-1, laliga-10, serie-a-13, ligue-1-23. Each competition yields its news, fixtures, results and (for leagues) its table. Find slugs on any competition page link.
Only read when mode = search. One entry per team: the link slug or the full team link, e.g. arsenal-2 or real-madrid-1915. Each team yields its news and its recent and upcoming matches.
Only read when mode = search. Also read the site-wide front-page news feed (the latest headlines across all competitions, in the selected language).
Only read when mode = my own links. Paste competition pages (optionally with /fixtures, /results or /table at the end), team pages, match pages, news article pages, or the home feed. Each link is read exactly as pasted; the page it names decides what is collected. Left untouched, this field holds one example of every supported link shape (home feed, competition news / fixtures / results / table, team news / fixtures / results, match, article, localized competition links). A ?page= parameter is not followed: the link is read from its first page and the run is flagged as partial scope.
[ "https://onefootball.com/en/news/serie-a-milan-2-4-bologna-mbangula-hat-trick-inflicts-first-amorim-league-defeat-43687788", "https://onefootball.com/en/home", "https://onefootball.com/en/competition/premier-league-9", "https://onefootball.com/en/competition/premier-league-9/fixtures", "https://onefootball.com/en/competition/premier-league-9/results", "https://onefootball.com/en/competition/premier-league-9/table", "https://onefootball.com/en/team/arsenal-2", "https://onefootball.com/en/team/arsenal-2/fixtures", "https://onefootball.com/en/team/arsenal-2/results", "https://onefootball.com/en/team/arsenal-2/news", "https://onefootball.com/en/match/2693644", "https://onefootball.com/de/competition/bundesliga-1", "https://onefootball.com/es/competicion/laliga-10"]Language of the news feeds, team pages and match pages. The site serves other languages only partially, so English is the one reliably complete edition; article links you paste are read in their own language when the site serves them.
Collect news articles from competitions, teams and the global feed.
Collect upcoming matches from competitions and teams.
Collect played matches with final scores from competitions and teams.
Collect league-table rows (position, played, won, drawn, lost, goal difference, points) from competitions that have one.
Keep only matches (by kickoff day) and news (by publish day) on or after this date, format YYYY-MM-DD. League table rows are never narrowed.
Keep only matches and news on or before this date, format YYYY-MM-DD.
Narrow match rows: scheduled (not started), live (in play or at half time), or finished. News is not affected.
Keep only rows whose title, preview, team names or competition name contain this text (case-insensitive).
Order rows within each source: date (kickoff or publish time) or title (news title or home team). Default keeps the site order.
Direction used when Sort by is not the site order.
Open each news article's own page and add the full article text to the record. Off by default: a run without it is cheaper and still carries titles, previews, publishers and timestamps.
Stop after this many records across the whole run (0 = the highest allowed cap, 100000; the walk ends earlier when the sources run out). Values above 100000 are read as 100000. News, matches and table rows all count.
Runaway guard: an upper bound on how many pages are read for any single news feed. Leave 0 to go as deep as the source serves, with the record cap above as the only real limit.
Connection used for every request. The site's content API answers on the standard connection pool; a residential pool also works but costs more per byte. You can also paste your own connection links.
{ "useApifyProxy": true}Paste the run id (or dataset id) of an earlier run of this Actor to continue it. Records that run already returned are skipped, so an interrupted large collection can finish without paying for the same rows twice. Leave empty for a normal run.
Turn this on for daily or weekly monitoring. The first run returns everything as NEW. Later runs return only NEW, UPDATED and REAPPEARED records, each labelled in a changeType column. Scores, table numbers and article text are watched, so a match that finished or a row that moved counts as UPDATED. Leave off for a normal one-off run.
Optional. Name this monitoring campaign to keep its memory stable, or to deliberately share one memory across differently configured runs. Leave empty and the memory is keyed on the run setup automatically.
Off by default. Turn on to also return records that have not changed since the last run, labelled UNCHANGED. This returns, and bills, rows you already have.
Off by default. Turn on to also return records that were present before and are no longer found, labelled EXPIRED (for example a match or article that scrolled out of every source). Only produced when a run covered its whole setup, so a capped or continued run never reports records as gone. This returns, and bills, extra rows.
Optional. Field names to leave out when deciding whether a record changed, in addition to the built-in handling (read order, source labels and relative times such as "9 minutes ago" already never trigger an UPDATED). Use it when another field turns out to be noisy in your setup. Use a dotted name such as homeTeam.name to ignore a field inside a nested object. The field is still returned in the output; it just does not count as a change.
Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify, Settings, API & Integrations, then select it here. Notion gets a rich page-per-item export; other connectors get a best-effort write or digest. Leave empty to skip; never changes the dataset output.
URL or id of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.