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 Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The Entity Sports Cricket API V2 provides season, competition, teams, matches, player, and statistical data for cricket. It adheres to RESTful principles and offers historical data for analysis. The base URL for accessing the API is https://www.doc.entitysport.com/cricket-api-v2. 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 pip install "dlt[workspace]" 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:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| matches | v2/matches/ | GET | response.items | List of matches (fixtures / live / results) with pagination |
| match_info | v2/match/info/ | GET | response | Single match details and scorecard |
| teams | v2/teams/ | GET | response.items | Teams list and profiles |
| players | v2/players/ | GET | response.items | Players list and profiles |
| competitions | v2/competitions/ | GET | response.items | Competitions / tournaments list |
| seasons | v2/seasons/ | GET | response.items | Seasons available to your subscription |
| squads | v2/match/squad/ | GET | response | Match squad / playing XI / fantasy credits |
| scorecard | v2/match/scorecard/ | GET | response | Match scorecard and innings data |
How do I authenticate with the Entity Sports Cricket API V2 API?
Clients obtain a time-limited access token by POSTing their access_key and secret_key to /v2/auth/; include the returned token on all requests as ?token=YOUR_TOKEN.
1. Get your credentials
- Sign up / sign in at https://www.entitysport.com or dashboard.entitysport.com.
- Purchase/subscribe to a plan to get access_key and secret_key.
- POST to /v2/auth/ with access_key and secret_key to receive response.token (short‑lived).
- Use the token as the token query parameter for subsequent requests; regenerate when expired.
2. Add them to .dlt/secrets.toml
[sources.entity_sports_cricket_api_v2_source] token = "your_short_lived_token_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 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:
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:
dlt pipeline entity_sports_cricket_api_v2_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 match_info 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", "token": token, }, }, "resources": [ {"name": "matches", "endpoint": {"path": "v2/matches/", "data_selector": "response.items"}}, {"name": "match_info", "endpoint": {"path": "v2/match/info/", "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.matches.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM entity_sports_cricket_api_v2_data.matches LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("entity_sports_cricket_api_v2_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 Entity Sports Cricket API V2 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 Entity Sports Cricket API V2?
Request dlt skills, commands, AGENT.md files, and AI-native context.