Load SportMonks Cricket data to DuckDB

SportMonks Cricket API provides comprehensive cricket data and statistics through a structured REST interface. Everything needed to build a working SportMonks Cricket → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your SportMonks Cricket to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from SportMonks Cricket to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the SportMonks Cricket API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

SportMonks Cricket API at a glance

These values come from the SportMonks Cricket API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the SportMonks Cricket API?

The API supports Bearer token authentication via the Authorization header (Authorization: Bearer ) and as a query parameter (api_token=). The Bearer token header is the recommended production approach.

1. Get your credentials

1. Log in to your MySportmonks account at https://my.sportmonks.com/. 2. Navigate to the API section in the dashboard sidebar. 3. Select 'Tokens' from the dropdown menu. 4. Enter a name for your new token in the 'Token name' field. 5. Click the 'Create' button. 6. Copy and store your API token immediately, as it will not be displayed again for security reasons.

2. Add them to .dlt/secrets.toml

Copy
[sources.sportmonks_cricket_source]
api_token = "your_api_token_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What SportMonks Cricket data can I load into DuckDB?

These are the SportMonks Cricket endpoints dlt can load into DuckDB:

---

How do I load only new SportMonks Cricket records?

SportMonks Cricket exposes id on v3/cricket/fixtures, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "fixtures", "endpoint": {
    "path": "v3/cricket/fixtures",
    "data_selector": "data",
    "incremental": {"cursor_path": "id", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated SportMonks Cricket pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /fixtures and /leagues from the SportMonks Cricket API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def sportmonks_cricket_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://cricket.sportmonks.com/api/v2.0/",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "fixtures", "endpoint": {"path": "v3/cricket/fixtures", "data_selector": "data"}},
            {"name": "players", "endpoint": {"path": "v3/cricket/players", "data_selector": "data"}}
        ],
    }
    yield from rest_api_resources(config)


def load_sportmonks_cricket_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="sportmonks_cricket_pipeline",
        destination="duckdb",
        dataset_name="sportmonks_cricket_data",
    )
    load_info = pipeline.run(sportmonks_cricket_source())
    print(load_info)


if __name__ == "__main__":
    load_sportmonks_cricket_to_duckdb()

Run it with python sportmonks_cricket_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query SportMonks Cricket data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("sportmonks_cricket_pipeline").dataset()
df = data.fixtures.df()
print(df.head())

SQL:

Copy
SELECT * FROM sportmonks_cricket_data.fixtures LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the SportMonks Cricket to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw SportMonks Cricket loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load SportMonks Cricket data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack