Is there a live roulette results API? How to get real-time spin data

A lot of the people who reach us from ChatGPT are after the same thing: a feed of live roulette results they can plug into their own code. Assistants often tell them there isn't a public one. There is, and we run it. GameData365 records every spin on 159 live roulette tables and every round of 31 crash games, and serves them as JSON. Below are the questions we hear most, answered with numbers we measured on 15 October 2026.

Is there an API for live roulette results?

Yes, though not from the studios. Evolution, Pragmatic Play and the rest don't sell a public results feed; their APIs are built for the licensed casinos that run their games. The data comes from trackers that record each round as it happens. We record 159 tables from 9 studios, and a spin shows up in our API about four seconds after the ball lands.

• 262,896roulette results a day
• 3.8 smedian, spin to API
• 98.8%of rounds captured on the median table
• 17.1Mroulette rounds in the archive

Open the API page →

Five ways to get live roulette data, compared

Search for “roulette API” and you get three quite different things mixed together: studio integration APIs, random-number simulators and real results feeds. Only a results feed gives you spins that actually happened on a table you can name.

Which providers and tables can you get?

Any of the 159 roulette tables on our games list, from 9 studios. You can take all of them or just the few you need. Ezugi, Pragmatic Play and Playtech have the most:

That covers the tables people ask about by name: Lightning Roulette, Immersive Roulette, XXXtreme Lightning Roulette and Auto-Roulette from Evolution, Mega Roulette 3000 and Speed Roulette 2 from Pragmatic Play, and local-language tables like Roleta Brasileira. You can also browse by studio: Evolution, Pragmatic Play, Playtech, Ezugi.

See the full list →

The API page shows a real response from the feed, refreshed every minute. See the live response →

How fast does a spin reach the API?

About four seconds. We timed 493 spins on 15 October 2026. The median gap between a round's timestamp and its first appearance in the API was 3.8 seconds, and 9 out of 10 showed up within 5.9. This is the route a result takes:

1. The ball landsThe dealer or the auto-wheel settles the round in the studio.
2. We record itFrom the table's own game feed: the round ID, the number and the time.
3. We check itDuplicates are dropped by round ID. A missed round is marked as a gap, never guessed.
4. Your app reads itThe next call to /v1/live returns it.≈ 3.8 s after the spin

There's no WebSocket to keep alive. One call to /v1/live returns the newest round on every table in your plan, and since a table only produces a new spin every half minute or so, polling every few seconds catches all of them:

That works out to one every 30 s on the fastest table, one every 47 s on a typical one and one every 2.6 min on the slowest, or 262,896 new results a day across all of them.

Speed only helps if the rounds are all there. Over the last 30 days the median table had 98.8% of its rounds captured, and 133 of 139 tables were above 95%. When a round is missing, the history shows a gap instead of papering over it, and any round we recovered later carries backfilled: true.

How much roulette history can you get?

Up to 30 days as standard, and longer if you ask. The archive behind the API holds 17.1 million roulette rounds; the oldest tables go back to February 2026. /v1/history gives you one table round by round, newest first, with a next_cursor for paging further back. History is filled in batches, so for the last few minutes use /v1/live.

{
  "status": "ok",
  "table_id": "lightning_roulette",
  "limit": 2,
  "count": 2,
  "next_cursor": "eyJ0cyI6ICIyMDI2LTEwLTE1IDA5OjU4OjU3Ii…",
  "window_days": 30,
  "rounds": [
    { "type": "round", "round_id": "1792058383528170", "number": 21,
      "color": "red", "parity": "odd", "dozen": 2, "column": 3,
      "half": "high", "timestamp": "2026-10-15T09:59:43Z", "backfilled": false },
    { "type": "round", "round_id": "1792058337685160", "number": 31,
      "color": "black", "parity": "odd", "dozen": 3, "column": 1,
      "half": "high", "timestamp": "2026-10-15T09:58:57Z", "backfilled": false }
  ]
}

Need a spreadsheet? One jq command turns the JSON into CSV:

curl -s -H "X-API-Key: YOUR_KEY" \
  "https://api.gamedata365.com/v1/history?table=lightning_roulette&provider=evolution&limit=100" \
  | jq -r '.rounds[] | select(.type == "round")
           | [.timestamp, .round_id, .number, .color] | @csv' > lightning.csv

If you only want a quick look, every table page shows its latest results and stats, for example Lightning Roulette.

What does a live roulette API response look like?

You send one API key in a request header and get plain JSON back. There's no SDK to install:

curl -H "X-API-Key: YOUR_KEY" \
  "https://api.gamedata365.com/v1/live?table=lightning_roulette&provider=evolution"

{
  "status": "ok",
  "provider": "evolution",
  "tables_count": 1,
  "server_time": "2026-10-15T10:20:48Z",
  "tables": [{
    "table_id": "lightning_roulette",
    "table_name": "Lightning Roulette",
    "provider": "evolution",
    "latest": {
      "round_id": "1792059618321529",
      "number": 30,
      "color": "red",
      "parity": "even",
      "dozen": 3,
      "column": 3,
      "half": "high",
      "timestamp": "2026-10-15T10:20:18Z",
      "backfilled": false
    }
  }]
}

• number: the pocket, 0 to 36.
• color, parity, dozen, column, half: already worked out for you. On zero the last four are null.
• round_id: changes when a new round has finished, which is how you spot a new spin.
• timestamp: when the round settled, in UTC.
• backfilled: true if we recovered the round after the fact.

The other calls look much the same. /v1/meta lists your tables with their 30-day coverage, and the crash calls return multipliers instead of pockets.

Is there an API for crash game results?

Yes, for 31 of them. Each round comes with its multiplier (2.31, say), a round ID and the time it settled. In our test week they produced 39,654 rounds a day between them; the busiest settle about 4,300 a day, roughly one every 20 seconds. We've kept 1.4 million rounds since 10 September 2026.

The games are JetX, Lucky Jet, RocketX, Rocket Queen, AirJet, MetaCrash, Spaceman, High Flyer, Crash, Rocketon, Avia Show, Aviator, Astronaut, Tropicana, StarX, Crime Empire, Fortune Crash, Maestro, Crasher, Cash Show, Starlight, Avixo, Skyward Storm, Skyward Deluxe, Space XY, Dragon's Crash, Treasure Jet, Cricket X, JetX3, Big Bass Crash and Aviatrix. You can watch them all on the live crash board, and our crash game history guide shows how often each one hits 10×, 100× and 1000×.

What people build with live roulette data

• Telegram channels and alert bots. Posting results, or pinging people when a run on a table gets long. Our live signal board does the same thing across every table.
• Results widgets. The last numbers of a table on a review or affiliate site, kept current.
• Stats apps and dashboards. For players who follow several tables and crash games at once.
• Research. Checking how wheels actually behave. One of ours: a number repeats on 2.71% of consecutive spins, against 2.70% for a fair wheel (the full count). Long dozen streaks follow the textbook curve too (every streak, measured).

Results data won't tell you the next spin, and anything that claims to is best avoided. It tells you what's happening on every table right now, and that's what all of the above is built on.

Scraping vs an API: what is the difference?

You can collect results yourself by reading web pages or a casino's game stream, and for a one-off look that works fine. As a long-term data source it runs into trouble:

• It breaks. Any change to a page or a stream stops the script, usually without warning.
• It misses rounds silently. When the script is down, nothing tells you which spins are missing.
• It's usually against the rules. Most sites ban bulk scraping in their terms (ours do too) and block it.

With an API you get one key and a format that doesn't change under you, with gaps marked instead of hidden. If you publish results on a website, your market's gambling-advertising rules still apply, so check them before you launch.

How to get access

1. Open the API page and look at the live response.
2. Tell us what you need: which games (a few tables, one studio, crash games or everything), how much history, and how fresh. Every round, once a minute or a few times a day all work.
3. Get a monthly price for exactly that, within one working day. Your key goes in the X-API-Key header.