Sports data API and live cricket data API
Betting sites need more than prices. This sports data API sends live cricket data, scorecards, match stats and results alongside the odds, so your match pages and settlement run from one feed. This page covers what data you get, how sports, competitions, events and markets fit together, and how the data arrives and stays current.
Live cricket data
- Ball-by-ball scorecards and commentary events
- Match stats for every innings
- Results that settle bets automatically
- Low-delay live TV where the match has it
Sports odds data
The same API carries Betfair match odds, Bookmaker rates and fancy and session markets, so odds and match data stay in step. The Cricket odds API page covers the betting markets in detail.
Beyond cricket
Live feeds also cover football, tennis, basketball, boxing and more, through the same integration. In the API each sport has a plain name: cricket, soccer, tennis, basketball, boxing. Your key receives the sports on your plan, and GET /v1/me lists them.
How the data is organised
Everything in the feed is one of a few kinds of thing, each with an id that never changes. Store them as you receive them.
| Id | What it is | Example |
|---|---|---|
cricket, soccer, … | A sport | cricket |
cp_… | A competition | One Day Internationals |
ev_… | An event: a match or a fixture | Pakistan v Sri Lanka |
mk_… | A market on that event | Match Odds, Bookmaker, 10 over run PAK |
rn_… | A runner (selection) in that market | Pakistan, The Draw, Yes |
Names can change; ids never do. Use the ids as keys in your own database.
What an event tells you
| Field | Meaning |
|---|---|
state | upcoming before the start, inplay once it is live |
start | Scheduled start, ISO 8601 UTC |
updatedAt | When any price in it last changed, in epoch milliseconds |
competition | The competition id and name |
markets | Every open market. A market leaves the event when it is settled or closed. |
All times are UTC. Convert to your players' time zone on your side.
A sample event
GET /v1/events?sport=cricket&state=inplay lists events without prices. One entry looks like this:
{
"id": "ev_k9wtucdybikxygkh",
"name": "Pakistan v Sri Lanka",
"sport": "cricket",
"competition": { "id": "cp_uumfx68hmdwne54u", "name": "One Day Internationals" },
"start": "2026-11-09T04:30:00Z",
"state": "inplay",
"inplay": true,
"updatedAt": 1794258468524,
"marketCount": 41
}Fetch GET /v1/events/{id} for the same event with every market and price.
How the data arrives
Request data over REST, or keep a live stream open with Server-Sent Events (SSE) so updates reach your site as they happen.
| Method | What you get | When to use it |
|---|---|---|
| Live stream (SSE) | Each event in full, then only what changed, plus results | Live sites with many events |
| Changes feed | The latest state of each market that changed since your token | Servers that cannot hold a stream open |
| REST snapshots | One event, or up to 50 in one call | Pages that load data on request |
| Results feed | Every result, in order, with a cursor | Settlement and catch-up |
With events=all, a live key's stream includes events that start later, so new fixtures reach you without a new request.
Staying current without waste
- Send
Accept-Encoding: gzip. Event snapshots shrink about tenfold. - Send the
ETagback asIf-None-Match. An unchanged event answers304 Not Modified. - On the stream, a
: heartbeatline arrives every 15 seconds. If nothing arrives for 45 seconds, reconnect. - Reconnect with
Last-Event-IDto receive exactly what you missed, results included. If it is too old, you get fresh snapshots, so your copy is always whole. - If your server falls behind, you get the latest state of each market, not a backlog of old ticks.
Errors you can act on
Errors come with a code you can act on and a sentence you can log. Every response carries an X-Request-Id to quote when you contact us.
| Status | Code | Meaning |
|---|---|---|
| 401 | unauthorized | No key, or a key we do not know |
| 403 | forbidden | The IP is not on your allowlist, or the key is for the other environment |
| 410 | resync | Your token is too old: take a fresh snapshot |
| 429 | rate_limited | Too many requests per second: wait for Retry-After |
| 503 | starting | The server is loading after a restart: retry in a few seconds |
The full list, with plan limits and allowances, is in the API reference.
Sandbox, then live
Your demo key works on the sandbox, which carries real, current events with prices 60 seconds old. Results are not delayed. A sandbox key has one stream, up to 5 events per stream and 2 requests per second. Live keys work on the live API with the limits of your plan. The sandbox is for building, not for running a site.
Who it is for
This sports data API is built for betting operators serving India, where cricket leads. It is a server-to-server API: keys work only from the IP addresses you register. Your apps and pages, in React, Vue, Flutter, iOS, Android or PHP, get their data from your own server.
Common questions
Is this a sports data API for India?
Yes. It is built for betting operators serving India, with IPL, BBL, PSL, CPL, SA20 and ICC events covered in cricket.
Can we take cricket data without odds?
Yes. You can take scorecards, match stats and live TV without the odds.
Which sports does the data cover?
Cricket, football, tennis, basketball, boxing and more.
Do ids change during a match?
No. Sport, competition, event, market and runner ids never change. Store them and use them as keys.
What format is the data in?
JSON, with gzip supported. All times are in UTC.
What happens if my connection drops?
Reconnect with the last message id in the Last-Event-ID header and you receive exactly what you missed. Standard EventSource clients do this for you.
How do I see my limits?
GET /v1/me returns your name, the sports on your plan and the limits on your key.