Bac Bo API: live results in JSON, with a free trial
How to use the Bac Bo results API: what each round contains, examples in Python and Node, the stream, history, pricing and a free 2-hour trial.
Published on October 18, 2026 · updated on October 31, 2026 · 6 min read
Anyone looking for a Bac Bo API almost always wants the same thing: the result of every Bac Bo Live round as soon as it ends, in a format a program understands, without opening the game, logging into a bookmaker or keeping a page scraper alive. That is exactly what LynxMetrics' Bac Bo results API delivers, and this guide shows what each round contains, how to make your first call and what it costs. If you only want to follow the table, the Bac Bo live results are open to anyone, for free.
What a Bac Bo API is
An API is an address on the internet that returns data to a program, not a page for a person to read. In Bac Bo's case, instead of watching the table, your bot, site or spreadsheet asks "what was the last round?" and gets the answer in JSON, with the Player and Banker dice, each side's total, who won and the tie multiplier. If you have never integrated an API, start with our guide on what an API is and how to connect to one.
LynxMetrics follows the live table round by round and stores every one of them in our database. That is why the API does not depend on anyone's login or on a third party's site, and the history has been kept since 14 October 2026, when the API went live.
What each round contains
Each round arrives like this, inside data:
{
"id": "v1792354840763",
"game": "bacbo-live",
"tableId": "BacBo00000000001",
"startedAt": "2026-10-18T20:20:25.593Z",
"settledAt": "2026-10-18T20:20:49.923Z",
"outcome": "banker",
"data": {
"player": { "dice": [1, 2], "score": 3 },
"banker": { "dice": [4, 5], "score": 9 },
"multiplier": null
}
}| Field | What it means |
|---|---|
id | Fixed identifier for the round; it never changes and keeps you from repeating messages |
startedAt and settledAt | Start and end of the round, in UTC |
outcome | Who won: player, banker or tie |
data.player.dice and data.banker.dice | Each side's two dice |
data.player.score and data.banker.score | The sum of each side's dice |
data.multiplier | What the tie paid (4, 6, 10, 25 or 88), or null when there was no tie |
The format is ours and stable, so if the source changes something behind the scenes, your integration stays the same.
The four endpoints
They all live at https://api.lynxmetrics.com/v1/bacbo-live and expect your key in the x-api-key header.
GET /latestreturns the most recent round, and it is what a bot polls every few seconds.GET /streamkeeps a connection open and pushes every round the moment it is stored, with the delivery timestamps and, if you ask for it, a heads-up when the table starts resolving the round, about 8 seconds before the result. It is the fastest and lightest path — see Bac Bo results in real time.GET /resultsreturns previous rounds in pages, newest first, withlimit(up to 250 on Pro and 1,000 on Business),beforeto go back in time andafterto sync without skipping or repeating rounds.GET /statscomputes on the fly the counts and percentages for Player, Banker and Tie and the current streak, over the latest rounds you ask for insample(up to 250 on Pro and 1,000 on Business).
The Bac Bo Live documentation lists every parameter and the meaning of each field.
Your first call
In the terminal, with the key you create in the dashboard:
curl https://api.lynxmetrics.com/v1/bacbo-live/latest \ -H "x-api-key: YOUR_KEY"
In Python, with the requests library:
import requests
response = requests.get(
"https://api.lynxmetrics.com/v1/bacbo-live/latest",
headers={"x-api-key": "YOUR_KEY"},
timeout=10,
)
round_ = response.json()["data"]
print(round_["outcome"], round_["data"]["player"]["score"], round_["data"]["banker"]["score"])In Node.js 18 or newer, with nothing to install:
const response = await fetch("https://api.lynxmetrics.com/v1/bacbo-live/latest", {
headers: { "x-api-key": process.env.LYNX_KEY },
});
const { data: round } = await response.json();
console.log(round.outcome, round.data.player.score, round.data.banker.score);How fast the result arrives
A Bac Bo Live round takes about 34 seconds from one start to the next, and the median we measured over more than 9,000 rounds was 33.8 seconds. The result shows up in the API about 4 seconds after the dice settle — measured in production, from settledAt to the data being stored and visible.
With /stream, the round arrives the moment it is stored, and every event carries the timestamps for each leg of the trip so you can check that number with your own clock. If you would rather poll /latest, every 2 or 3 seconds is enough not to miss anything, and it pays to send the ETag from the last response in the If-None-Match header: the API answers 304 with no body when nothing has changed, which keeps your bot light.
What if I wanted a WebSocket?
Many people search for a "Bac Bo API with WebSocket" because they want the result pushed to their program, without polling. /stream does exactly that, only with SSE: the connection stays open and each round arrives the moment it is stored. The difference is that SSE is plain HTTP, so it goes through proxies and CDNs, reconnects on its own and works in Python, Node or PHP with no special library. For results, which only flow one way, it solves the same problem with fewer moving parts — the reasoning is in real-time results.
History and statistics
An API's value is not only in the latest result, which any broadcast shows for free. It is in the complete, gap-free history. Statistics pages tend to keep few rounds, and in a round-by-round comparison we showed that one of the best-known sites was leaving out about 20% of the rounds in its own list. At LynxMetrics every round read is kept, and you query it with /results as far back as your plan allows.
To understand what to do with that data, see our articles on Bac Bo history and statistics with real data.
What the Bac Bo API costs
| Plan | Price | For whom | History | Per request | Requests per minute |
|---|---|---|---|---|---|
| Pro | R$ 21.90 per month | Bots and groups | 7 days | up to 250 rounds | 60 |
| Business | R$ 49.90 per month | Sites and larger operations | full | up to 1,000 rounds | 400 |
You pay by Pix or card, and each subscription is a project with its own keys and its own limit, so you can keep one project per bot. The details are in how the subscription works.
How to try it for free
Create your account, confirm your email and open the Bac Bo Live trial in the dashboard. You get a key that works for 1 hour with Pro limits, no card. If you like it, you subscribe to the same project and the key keeps working, so the code you wrote during the trial does not change.
What you can build
- A Bac Bo Telegram bot that posts every result to your group.
- An automated results and statistics group, with no black-box bot.
- A site, dashboard or spreadsheet with live results.
- The Bac Bo charts, such as the Bead Road, drawn from the JSON.
The same account covers the other tables in the catalogue, which answer in the same format and on the same endpoints: Lightning Baccarat and Pragmatic Play's Baccarat 1.
Frequently asked questions
- Is there a free Bac Bo API?
You can try LynxMetrics' Bac Bo Live API free for 2 hours, with Pro plan limits and no card, and repeat the trial every 24 hours. For daily use, plans start at R$ 21.90 per month.
- Does the Bac Bo API work with Python, Node or PHP?
It works in any language that can make an HTTP request, because the response is plain JSON. The examples here are in Python and Node, and the same request works in PHP, Java, Go or even Google Sheets.
- How long after the round does the result appear in the API?
About 4 seconds after the dice settle, measured in production, while a round takes about 34 seconds. Anyone using the /stream endpoint receives the round the moment it is stored, and the stream, if you open the connection with ?phases=1, also warns about 8 seconds earlier that the table started resolving the round.
- Does the API predict the next round's result?
No. The API delivers results and statistics for what already happened. Every round is random, and no pattern in the history points to the next one.
For adults 18 and over only. LynxMetrics is not affiliated with Evolution or with the casinos that offer Bac Bo Live, and it only sells data and stats, never predictions or betting tips, because every round is random and past results do not predict the next one.
Read also
- Bac Bo results in real time: ~4 seconds per round
How to receive every Bac Bo Live round the moment it is stored: the measured delay, the 8s heads-up before the result, and ready-to-run Python code.
- Bac Bo Telegram bot: build one with Python, step by step
A complete tutorial for building a Bac Bo Telegram bot: BotFather, live results from the API, messages that never repeat, Discord, and where to host it 24/7.
- Bac Bo history: LynxMetrics and CasinoScores compared
We compared 72 hours of Bac Bo Live between LynxMetrics and the public CasinoScores list on 18/10/2026, with the original files for you to check.