Lightning Baccarat API: endpoints, examples and limits
How LynxMetrics' Lightning Baccarat API works: every round's cards in JSON, the four endpoints, Python and Node examples, history, pricing and a free trial.
Published on October 30, 2026 · 7 min read
Anyone looking for a Lightning Baccarat API almost always wants the same thing: every round's cards the moment the hand closes, in a format a program understands, without opening the game, logging into a casino or keeping a page scraper alive. That is what the Lightning Baccarat API from LynxMetrics delivers, live since 30 October 2026. This guide covers what each round contains, how to make your first call, how fast the result arrives and what it costs.
What the Lightning Baccarat API delivers
The table is Evolution's Lightning Baccarat, and LynxMetrics follows it live, hand by hand, recognising every card on the felt. When the hand closes, the round is stored with the Player and Banker cards in the order they came out, each side's score, the winner, the pairs and the natural. None of this depends on anyone's login or on a third-party website, which is why the format is ours and stable: if the source changes something behind the scenes, your integration stays the same.
If you have never integrated an API before, start with our guide on what an API is and how to connect to one. And if you are weighing a scraper against a subscription, we have an article on scraping or an API.
What each round contains
A round arrives like this:
{
"id": "v1793371825421",
"game": "lightning-baccarat",
"tableId": "LightningBac0001",
"startedAt": "2026-10-30T18:10:25.421Z",
"settledAt": "2026-10-30T18:10:58.903Z",
"outcome": "player",
"data": {
"player": { "cards": ["KH", "9D"], "score": 9, "pair": false },
"banker": { "cards": ["5C", "2S", "7H"], "score": 4, "pair": false },
"natural": true
}
}| Field | What it means |
|---|---|
id | Fixed identifier for the round; it never changes and keeps you from posting the same hand twice |
startedAt and settledAt | Start and end of the round, in UTC |
outcome | Who won: player, banker or tie |
data.player.cards and data.banker.cards | Each side's cards, two or three, in the order they came out |
data.player.score and data.banker.score | The side's score, from 0 to 9 |
data.player.pair and data.banker.pair | true when the side's first two cards have the same value |
data.natural | true when either side made 8 or 9 on two cards, which ends the hand with no third card |
Each card is a two-letter string: the rank in A23456789TJQK (T is the ten) and the suit in CDHS — clubs, diamonds, hearts and spades. So "KH" is the king of hearts and "TD" is the ten of diamonds. Turning that into a pretty name on screen is a two-liner:
RANKS = {"A": "A", "T": "10", "J": "J", "Q": "Q", "K": "K"}
SUITS = {"C": "♣", "D": "♦", "H": "♥", "S": "♠"}
def pretty(card):
rank, suit = card[0], card[1]
return RANKS.get(rank, rank) + SUITS[suit]
print(" ".join(pretty(c) for c in ["KH", "9D"])) # K♥ 9♦The score comes precomputed, but the rule is plain baccarat: an ace is 1, tens and face cards are 0, everything else is worth its number, and the side's score is the sum modulo 10.
The four endpoints
They all live at https://api.lynxmetrics.com/v1/lightning-baccarat and expect your key in the x-api-key header.
GET /latestreturns the most recent round.GET /streamkeeps a connection open and pushes every round the moment it is stored, with delivery timestamps and a heads-up, if you ask for it, when the table starts resolving the hand. It is the fastest path and the lightest one, because it does not spend a request per check — there is a whole article about it in live 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. See Lightning Baccarat history.GET /statscomputes on the fly the counts and percentages for Player, Banker and Tie, the current streak, how many rounds had a pair on each side and how many ended in a natural, over the latest rounds you ask for insample(up to 250 on Pro and 1,000 on Business). See Lightning Baccarat statistics.
The Lightning Baccarat documentation lists every parameter and the meaning of each field, and it is also available in Markdown for anyone reading with an agent.
Your first call
In the terminal, with the key you create in the dashboard:
curl https://api.lynxmetrics.com/v1/lightning-baccarat/latest \ -H "x-api-key: YOUR_KEY"
In Python, with the requests library:
import requests
response = requests.get(
"https://api.lynxmetrics.com/v1/lightning-baccarat/latest",
headers={"x-api-key": "YOUR_KEY"},
timeout=10,
)
hand = response.json()["data"]
print(hand["outcome"], hand["data"]["player"]["score"], hand["data"]["banker"]["score"])In Node.js 18 or newer, with nothing to install:
const response = await fetch("https://api.lynxmetrics.com/v1/lightning-baccarat/latest", {
headers: { "x-api-key": process.env.LYNX_KEY },
});
const { data: hand } = await response.json();
console.log(hand.outcome, hand.data.player.cards.join(" "), hand.data.banker.cards.join(" "));It works in any language that can make an HTTP request, because the response is plain JSON: PHP, Java, Go, C#, Ruby, even a spreadsheet's IMPORTDATA.
How fast the result arrives
A Lightning Baccarat round takes about 35 seconds, and the result shows up in the API about 5 seconds after the hand closes — that is what we measured in production, from settledAt to the data being stored and visible. Almost all of those 5 seconds are the reader making sure of what is on the table; our database accounts for a fraction of it.
There are two ways to follow along live. /stream delivers the round the moment it is stored and is the fastest. If you would rather poll /latest, every 3 seconds is plenty, and it pays to send the ETag from the previous response in the If-None-Match header: when nothing has changed the API answers 304 with no body, which keeps your program light.
What the Lightning Baccarat API costs
| Plan | Price | For whom | History | Per request | Per minute | Connections |
|---|---|---|---|---|---|---|
| Pro | R$ 21.90 per month | Bots and groups | 7 days | up to 250 rounds | 60 requests | 1 |
| Business | R$ 49.90 per month | Sites and larger operations | full | up to 1,000 rounds | 400 requests | 5 |
Billing is in Brazilian reais, 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 connections column is how many /stream connections the same key can hold open at once. The details are in how the subscription works.
How to try it for free
Create the account, confirm your email and open the Lightning Baccarat trial in the dashboard. You get a key that works for 2 hours with Pro limits, no card required, and you can repeat the trial every 24 hours. If you like it, you subscribe to the same project and the key keeps working: the code you wrote during the trial does not change.
What you can build
- A Lightning Baccarat Telegram bot that posts every hand to your group, cards included.
- A dashboard or site with the Bead Road and live percentages, drawn straight from the JSON.
- A spreadsheet or database with the full history, to study the rounds at your own pace.
- Streak, pair and natural alerts, each one on top of a field that already comes ready.
And if you follow other tables too, the same account covers them: the Bac Bo Live API and the Baccarat 1 API, Pragmatic Play's classic baccarat, answer in the same format, with the same endpoints. If you are choosing between the two baccarat tables, there is a comparison in Baccarat 1 vs Lightning Baccarat.
Frequently asked questions
- Is there a free Lightning Baccarat API?
You can try LynxMetrics' Lightning Baccarat 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 API include the Lightning multipliers?
No. The API delivers the cards, the score, the winner, the pairs and the natural of every hand. Lightning multipliers are drawn each round and change the payout rather than the cards, so they are outside our format.
- How long after the round does the result appear in the API?
About 5 seconds after the hand closes, measured in production. A round takes roughly 35 seconds, and anyone using the /stream endpoint receives it the moment it is stored.
- Which languages can I use with the Lightning Baccarat API?
Any language that can make an HTTP request, because the response is plain JSON. The examples here are in Python and Node.js, and the same request works in PHP, Java, Go, C# or a spreadsheet.
- How far back does the Lightning Baccarat history go?
To 30 October 2026, when the API went live. Every round read since then is kept: the Pro plan queries the last 7 days and Business the full history.
For adults 18 and over only. LynxMetrics is not affiliated with Evolution or with the casinos that offer Lightning Baccarat, 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
- Lightning Baccarat results: every hand in ~5 seconds
How to receive every Lightning Baccarat round the moment it closes: the measured delay, the heads-up before the result, and code in Python and Node.
- How to build a Lightning Baccarat Telegram bot
Step by step to post every Lightning Baccarat round to a Telegram group: create the bot, hook it to the API stream, format the cards and avoid repeats.
- Lightning Baccarat accuracy: a 143-round audit
The audit we ran before opening the Lightning Baccarat API: 143 rounds checked against an external source and frame by frame, and what we still watch daily.