Entity Sports Cricket API V2 Python API Docs | dltHub

Build a Entity Sports Cricket API V2-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Entity Sports Cricket API V2 provides comprehensive cricket data including seasons, competitions, matches, teams, and statistics through a RESTful interface. The REST API base URL is https://restapi.entitysport.com/v2/ and all requests require a short-lived token passed as the query parameter token.

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 Entity Sports Cricket API V2 data in under 10 minutes.


What data can I load from Entity Sports Cricket API V2?

Here are some of the endpoints you can load from Entity Sports Cricket API V2:

ResourceEndpointMethodData selectorDescription
competitions/v2/competitionsGETresponseList of all competitions
matches_upcoming/v2/matches/upcomingGETresponseList of upcoming matches
player_ranks/v2/players/ranksGETresponseList of player rankings
squads/v2/competitions/{cid}/squadsGETresponseList of team squads for a competition
matches_live/v2/matches/{mid}/liveGETresponseReal-time live match details

How do I authenticate with the Entity Sports Cricket API V2 API?

Authentication requires obtaining a short-lived token by sending a POST request to /v2/auth/ with access_key and secret_key in the body. This token must then be passed as a query parameter named 'token' in all subsequent API requests.

1. Get your credentials

  1. Register for an account at the Entity Sports website. 2. Verify your email address through the link sent to your inbox. 3. Log in to the Entity Sports dashboard using your verified credentials. 4. Navigate to the Plans section to select a subscription plan. 5. Once the subscription is processed, go to the Application section on the dashboard to locate your API access credentials, including your access key and secret key.

2. Add them to .dlt/secrets.toml

[sources.entity_sports_cricket_api_v2_source] token = "REPLACE_ME"

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 Entity Sports Cricket API V2 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 entity_sports_cricket_api_v2_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline entity_sports_cricket_api_v2_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset entity_sports_cricket_api_v2_data The duckdb destination used duckdb:/entity_sports_cricket_api_v2.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 /v2/auth/ and /?token=[ACCESS_TOKEN] (for data requests) from the Entity Sports Cricket API V2 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 entity_sports_cricket_api_v2_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://restapi.entitysport.com/v2/", "auth": {"type": "api_key", "api_key": token, "name": "token"}, }, "resources": [ {"name": "competitions", "endpoint": {"path": "v2/competitions", "data_selector": "response"}}, {"name": "matches_upcoming", "endpoint": {"path": "v2/matches/upcoming", "data_selector": "response"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="entity_sports_cricket_api_v2_pipeline", destination="duckdb", dataset_name="entity_sports_cricket_api_v2_data", ) load_info = pipeline.run(entity_sports_cricket_api_v2_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("entity_sports_cricket_api_v2_pipeline").dataset() sessions_df = data.competitions.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM entity_sports_cricket_api_v2_data.competitions LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("entity_sports_cricket_api_v2_pipeline").dataset() data.competitions.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 Entity Sports Cricket API V2 data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Entity Sports Cricket API V2?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines