SportRadar Python API Docs | dltHub
Build a SportRadar-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Sportradar provides comprehensive sports data, including real-time feeds, statistics, and odds, delivered via RESTful APIs. The REST API base URL is https://api.sportradar.com and most Sportradar APIs require an API key in the 'x-api-key' header, though some services use OAuth 2.0 Bearer tokens.
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 add "dlt[hub]" and start loading SportRadar data in under 10 minutes.
What data can I load from SportRadar?
Here are some of the endpoints you can load from SportRadar:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| season_summaries | /seasons/summaries | GET | Returns a list of season summaries. Uses start for pagination. | |
| match_summaries | /matches/summaries | GET | Returns match summary data. Uses start for pagination. | |
| player_profiles | /players/profile | GET | Fetches player details. Uses start for pagination. | |
| schedule | /schedule | GET | Returns upcoming event schedule. Uses start for pagination. | |
| venue_details | /venues/details | GET | Returns specific venue information. Uses start for pagination. |
How do I authenticate with the SportRadar API?
Sportradar APIs generally use API key authentication, where the key must be passed in the 'x-api-key' request header. Some specialized services (e.g., Insight Tech Services, Common IAM) use OAuth 2.0 with a 'Bearer' token in the 'Authorization' header.
1. Get your credentials
- Navigate to the Sportradar Developer Portal (https://console.sportradar.com/) and create an account or log in. 2. Once logged in, navigate to the 'Your Account' or dashboard section where your applications are managed. 3. Select your desired application (or create a new one for testing/production environments). 4. Locate your Master API Key within the application credentials area. 5. Use the 'Copy' icon to copy the key to your clipboard. 6. Ensure you have subscribed to the specific product/API you intend to use.
2. Add them to .dlt/secrets.toml
[sources.sportradar_source] api_key = "your_actual_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 init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub 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:
uv run dlthub ai toolkit install rest-api-pipeline
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 SportRadar 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:
uv run python sportradar_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline sportradar_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset sportradar_data The duckdb destination used duckdb:/sportradar.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub 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 competitions and schedule from the SportRadar 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 sportradar_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.sportradar.com", "auth": {"type": "api_key", "api_key": api_key, "name": "x-api-key", "location": "header"}, }, "resources": [ {"name": "season_summaries", "endpoint": {"path": "seasons/summaries"}}, {"name": "match_summaries", "endpoint": {"path": "matches/summaries"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sportradar_pipeline", destination="duckdb", dataset_name="sportradar_data", ) load_info = pipeline.run(sportradar_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("sportradar_pipeline").dataset() sessions_df = data.season_summaries.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM sportradar_data.season_summaries LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("sportradar_pipeline").dataset() data.season_summaries.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 SportRadar 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 harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for SportRadar?
Request dlt skills, commands, AGENT.md files, and AI-native context.