Load UTR Sports data to DuckDB

UTR Sports Engage API allows third-party applications to retrieve player ratings, profile information, and manage results via an OAuth2-authorized REST interface. Everything needed to build a working UTR Sports → 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 UTR Sports 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 UTR Sports 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 UTR Sports 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.

---

UTR Sports API at a glance

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

---

How do I authenticate with the UTR Sports API?

The UTR Sports Engage API uses OAuth2 to authorize third-party applications, requiring an access token provided in the Authorization header as a Bearer token.

1. Get your credentials

To obtain credentials for the UTR Sports Engage API, navigate to the official UTR Sports API Developer Application page. Complete and submit the application form. Upon approval, UTR Sports will provide you with a Client ID and Client Secret. Ensure you have agreed to the API Terms & Conditions and implemented the required OAuth2 flow for secure user authentication.

2. Add them to .dlt/secrets.toml

Copy
[sources.utr_sports_source]
access_token = "your_access_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 UTR Sports data can I load into DuckDB?

These are the UTR Sports endpoints dlt can load into DuckDB:

---

How do I load only new UTR Sports records?

The UTR Sports API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "player_search", "endpoint": {
    "path": "v2/search/players",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "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 UTR Sports pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /v2/search/players and /v1/player/{id}/profile from the UTR Sports API into DuckDB:

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

@dlt.source
def utr_sports_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://www.utrsports.net/api/v1/",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "player_search", "endpoint": {"path": "v2/search/players", "data_selector": "hits"}},
            {"name": "player_info", "endpoint": {"path": "v1/player/{user_id}"}}
        ],
    }
    yield from rest_api_resources(config)


def load_utr_sports_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="utr_sports_pipeline",
        destination="duckdb",
        dataset_name="utr_sports_data",
    )
    load_info = pipeline.run(utr_sports_source())
    print(load_info)


if __name__ == "__main__":
    load_utr_sports_to_duckdb()

Run it with python utr_sports_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 UTR Sports 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("utr_sports_pipeline").dataset()
df = data.player_search.df()
print(df.head())

SQL:

Copy
SELECT * FROM utr_sports_data.player_search LIMIT 10;

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

---

How do I deploy the UTR Sports 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 UTR Sports 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 UTR Sports 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