# Bundesliga Fixtures, Results and Standings Exporter (`zinin/bundesliga-fixtures-results-standings-exporter`) Actor

Export Bundesliga match schedules, reported scores and season standings from OpenLigaDB with team IDs, UTC dates, source evidence and ODbL attribution.

- **URL**: https://apify.com/zinin/bundesliga-fixtures-results-standings-exporter.md
- **Developed by:** [Tim Zinin](https://apify.com/zinin) (community)
- **Categories:** Games
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.70 / 1,000 football data row delivereds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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

```json
{"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:

```json
{"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:

```json
{"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 an `After90Minutes` result. Missing scores remain null, not 0:0. Intermediate results remain in `results`; 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](https://www.openligadb.de/), made available under the [Open Database License (ODbL 1.0)](https://opendatacommons.org/licenses/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](https://github.com/OpenLigaDB/OpenLigaDB-Samples).

# Actor input Schema

## `demo` (type: `boolean`):

Invented output without source requests or result events. Ignores season, mode, round and maxItems, including form defaults. A configured start charge may apply.

## `season` (type: `integer`):

Required for real data. 2026 means 2026/2027. Unavailable seasons may produce empty sources.

## `mode` (type: `string`):

Defaults to both. Table rows are the latest source table for the selected season, not a historical matchday table.

## `round` (type: `integer`):

Optional; valid only with mode:matches. All source matches are validated before this filter is applied.

## `maxItems` (type: `integer`):

Defaults to 500. Matches precede table rows in both mode. Result events are requested only for delivered real rows. Also set Max total charge.

## Actor input object example

```json
{
  "season": 2026,
  "mode": "both",
  "maxItems": 500
}
```

# Actor output Schema

## `results` (type: `string`):

Real match and standing rows, plus unbilled diagnostics. Inspect recordType/isDemo.

## `summary` (type: `string`):

Read collectionComplete, deliveryComplete and limits. Season completeness is not independently verified.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "season": 2026,
    "mode": "both",
    "maxItems": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("zinin/bundesliga-fixtures-results-standings-exporter").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "season": 2026,
    "mode": "both",
    "maxItems": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("zinin/bundesliga-fixtures-results-standings-exporter").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "season": 2026,
  "mode": "both",
  "maxItems": 500
}' |
apify call zinin/bundesliga-fixtures-results-standings-exporter --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zinin/bundesliga-fixtures-results-standings-exporter"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/PI0fDuzWOEg98WyLI/builds/Gmb5TiyjiJaIK5G2b/openapi.json