Bundesliga Fixtures, Results and Standings Exporter
Pricing
from $1.70 / 1,000 football data row delivereds
Bundesliga Fixtures, Results and Standings Exporter
Export Bundesliga match schedules, reported scores and season standings from OpenLigaDB with team IDs, UTC dates, source evidence and ODbL attribution.
Bundesliga Fixtures, Results and Standings
Export Bundesliga match schedules, reported scores and the latest season table from OpenLigaDB as JSON or CSV. Rows retain match/team identifiers, source timestamps, source hashes and attribution for reuse in football sites and research pipelines.
This is an independent exporter of community-maintained data. It does not verify results with the competition organizer or provide betting predictions. Future kickoff times can change.
Collect a season
{"season": 2026, "mode": "both", "maxItems": 500}
The season is its starting year: 2026 selects 2026/2027. V1 supports the first Bundesliga (bl1) only. An explicit season is required for real collection; it never silently switches years. The service accepts years 2002–2099, but the source may return no data for an unavailable season.
mode is matches, standings or both (default). maxItems is 1–500, default 500, and limits delivered billable rows after source validation. In both mode matches come first, then table rows. All requested source responses are downloaded and validated before output; a small output limit does not reduce source download size.
For one matchday:
{"season": 2026, "mode": "matches", "round": 3, "maxItems": 9}
round accepts 1–34 and requires mode: "matches". Standings are the latest source table for the selected season, not a reconstruction of the table after a requested matchday.
For an invented offline example with no result charge or source request:
{"demo": true}
You can also enable the demo checkbox in the input form. Demo mode ignores the known collection fields (season, mode, round, maxItems), including form defaults; unknown fields are rejected. A configured platform start charge may still apply.
Output
football_match: source match/league/group IDs, round, home/away team IDs and names, supplied UTC kickoff, raw local kickoff and source revision, finished flag, score variants and warnings. A final score is exposed only when the source marks the match finished and provides anAfter90Minutesresult. Missing scores remain null, not 0:0. Intermediate results remain inresults; they are not verified final scores.football_standing: team ID/name, source table position, played/won/drawn/lost, goals and points. Position preserves the source array order. The difference from three points per win and one per draw is retained without guessing a penalty or adjustment reason. Tables and matches are separate requests, not an atomic synchronized snapshot.diagnostic: unbilled empty results, source errors or output/budget limits.
The synthetic demo also uses recordType: football_match; exclude rows with isDemo: true when importing real data. Its OUTPUT.outcome is demo and collectionComplete is false because it makes no source requests.
The default Dataset contains the data. OUTPUT in the default key-value store contains collection and delivery counts, source hashes and incomplete-run indicators, without duplicating paid football data. collectionComplete means the requested endpoints were retrieved and parsed. It does not establish complete or official season coverage. Results contain no team logos or individual goal events.
Pricing and recovery
Each real match or standing row delivered requests one result-found event. Repeated snapshots are billable again. Demo and diagnostic rows request no result event. Check current pricing in Apify and set a Max total charge appropriate to the desired row count.
At the initial Free-tier rates of $0.002 per data row and $0.005 per start, a source snapshot containing 306 matches and 18 standings costs $0.653 in Actor events. Source coverage and current pricing can change; a lower Max total charge returns only the rows that fit.
Dataset billing.resultEventRequested describes whether a result event was intended for that row. billing.settlement: "unconfirmed_at_write" is recorded before the charge acknowledgement and is not updated afterwards. It does not mean that a completed run remains unpaid. Check the run's actual charged-event counters and, when present, OUTPUT.confirmedResultEvents for confirmation.
If the money limit or maxItems stops delivery, the Dataset contains the rows already delivered, and OUTPUT shows deliveryComplete: false. An empty selection has no result charge. If any requested source cannot be retrieved or validated, the run fails before delivering paid data. If storage or charging becomes uncertain, the Actor does not retry the write or automatically replay the run. Inspect existing rows and event counters before starting another run.
OUTPUT may be absent after a timeout, process termination or uncertain storage acknowledgement. Its absence does not prove that no rows were delivered or charged. Inspect the existing Dataset and run event counters before rerunning.
Source requests are sequential, at least one second apart within a run, with a 20-second deadline and 8 MiB response bound per endpoint. There are no automatic source retries or cross-run cache. Parallel runs have independent request clocks.
Validation rejects duplicate identities, invalid numeric fields and inconsistent table arithmetic (played != won + drawn + lost or an inconsistent goal difference). In both mode, such a table error also withholds match rows before any result charge. Missing final scores are a different case: the match remains a useful fixture and carries a warning. Source hashes cover the decoded HTTP response body, not compressed wire bytes. Row IDs identify a match or season/team; use source.retrievedAt and source.sha256 to distinguish repeated snapshots.
Source and data license
Contains information from OpenLigaDB, made available under the Open Database License (ODbL 1.0). The data license applies independently of charges for using this Actor; retain source attribution and consult the license when redistributing data or derived databases. Every real data row includes the license and source links. OpenLigaDB is a community source, not the Bundesliga organizer.
Routes: https://api.openligadb.de/getmatchdata/bl1/{season} and https://api.openligadb.de/getbltable/bl1/{season}. See the source API documentation.