SoccerData Python API Docs | dltHub
Build a SoccerData-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
SoccerData API provides live scores and league stats from over 125 leagues. It includes live scores, league stats, and pre-match content. The documentation is available at https://soccerdataapi.com/docs/. The REST API base URL is https://api.soccerdataapi.com and all requests require an API key provided as auth_token query parameter.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading SoccerData data in under 10 minutes.
What data can I load from SoccerData?
Here are some of the endpoints you can load from SoccerData:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| countries | /country/ | GET | results | List of available countries (paginated: count, next, previous, results) |
| leagues | /league/ | GET | results | List of leagues (filterable by country_id) |
| seasons | /season/ | GET | results | Seasons for a league (filterable by league_id) |
| stages | /stage/ | GET | results | Season stages (filterable by league_id and season) |
| groups | /group/ | GET | results | Groups for a stage (filterable by stage_id) |
| stadiums | /stadium/ | GET | Retrieve stadiums by team_id or stadium_id; single‑stadium response is an object (no results key) | |
| teams | /team/ | GET | Retrieve team by team_id; team endpoint returns an object when id provided | |
| players | /player/ | GET | Retrieve player by player_id; single player returns object | |
| transfers | /transfers/ | GET | results | Transfers by team_id |
| head_to_head | /head-to-head/ | GET | results | Head‑to‑head stats between two teams (team_1_id & team_2_id) |
| standings | /standing/ | GET | results | League standings by league_id |
| livescores | /livescores/ | GET | results | Live matches for current day (auth_token required) |
| matches | /matches/ | GET | results | Matches by date or league_id (optional season param) |
| match | /match/ | GET | Match details by match_id (single object response) | |
| match_preview | /match-preview/ | GET | Match preview by match_id | |
| upcoming_match_previews | /match-previews-upcoming/ | GET | Upcoming match previews (returns array of league objects each containing match_previews array) |
How do I authenticate with the SoccerData API?
The API uses an API key (auth_token) that must be included in every request as a query parameter (auth_token=YOUR-AUTH-TOKEN). Requests must include the header 'Accept-Encoding: gzip' because JSON responses are gzip‑compressed.
1. Get your credentials
- Sign up for an account at https://soccerdataapi.com.
- After logging in, go to your account/dashboard or API settings to locate or generate an API key.
- Copy the API key and use it as the auth_token query parameter in requests.
2. Add them to .dlt/secrets.toml
[sources.soccerdata_source] auth_token = "your_api_key_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the SoccerData API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python soccerdata_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline soccerdata_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset soccerdata_data The duckdb destination used duckdb:/soccerdata.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline soccerdata_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads matches and livescores from the SoccerData API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def soccerdata_source(auth_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.soccerdataapi.com", "auth": { "type": "api_key", "auth_token": auth_token, }, }, "resources": [ {"name": "matches", "endpoint": {"path": "matches/", "data_selector": "results"}}, {"name": "livescores", "endpoint": {"path": "livescores/", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="soccerdata_pipeline", destination="duckdb", dataset_name="soccerdata_data", ) load_info = pipeline.run(soccerdata_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("soccerdata_pipeline").dataset() sessions_df = data.matches.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM soccerdata_data.matches LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("soccerdata_pipeline").dataset() data.matches.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load SoccerData data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for SoccerData?
Request dlt skills, commands, AGENT.md files, and AI-native context.