Blog · Baccarat 1

Baccarat 1 API (Pragmatic Play): live results in JSON

How LynxMetrics' Baccarat 1 API works: every hand from Pragmatic Play's table in JSON, the four endpoints, Python and Node examples, pricing and a free trial.

Published on November 2, 2026 · 8 min read

Como usar a API da Baccarat 1 da Pragmatic Play: a chave, o /latest e os campos · on YouTube

Anyone looking for a Baccarat 1 API almost always wants the same thing: every hand'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 Baccarat 1 API from LynxMetrics delivers, live since 1 November 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 Baccarat 1 API delivers

The table is Pragmatic Play's Baccarat 1, and LynxMetrics follows it live, hand by hand: 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": "v1793553361643",
  "game": "baccarat-1",
  "tableId": "pragmatic-baccarat-1",
  "startedAt": "2026-11-01T17:15:58.000Z",
  "settledAt": "2026-11-01T17:16:21.643Z",
  "outcome": "player",
  "data": {
    "player": { "cards": ["JS", "8H"], "score": 8, "pair": false },
    "banker": { "cards": ["2C", "KC"], "score": 2, "pair": false },
    "natural": true
  }
}
FieldWhat it means
idFixed identifier for the round; it never changes and keeps you from posting the same hand twice
gameAlways baccarat-1, handy if your program handles more than one table
startedAt and settledAtStart and end of the round, in UTC
outcomeWho won: player, banker or tie
data.player.cards and data.banker.cardsEach side's cards, two or three, in the order they came out
data.player.score and data.banker.scoreThe side's score, from 0 to 9
data.player.pair and data.banker.pairtrue when the side's first two cards have the same value
data.naturaltrue when either side made 8 or 9 on two cards, which ends the hand with no third card

In the example round the Player got a jack and an 8: the jack is worth 0, so that is 8 points on two cards, which is a natural and ends the hand on the spot. The Banker stayed on 2 and drew nothing, because there is no third card after a natural. The whole rule is in how Baccarat 1 works.

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 "JS" is the jack of spades and "KC" is the king of clubs. 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 ["JS", "8H"]))  # J♠ 8♥

The score comes precomputed, but the arithmetic 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/baccarat-1 and expect your key in the x-api-key header.

  • GET /latest returns the most recent hand.
  • GET /stream keeps a connection open and pushes every hand the moment it is stored, with delivery timestamps. 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 Baccarat 1 results live.
  • GET /results returns previous hands in pages, newest first, with limit (up to 250 on Pro and 1,000 on Business), before to go back in time and after to sync without skipping or repeating rounds. See Baccarat 1 history.
  • GET /stats computes on the fly the counts and percentages for Player, Banker and Tie, the current streak, how many hands had a pair on each side and how many ended in a natural, over the latest rounds you ask for in sample (up to 250 on Pro and 1,000 on Business). See Baccarat 1 statistics.

The Baccarat 1 documentation lists every parameter and the meaning of each field, and it is also available in Markdown for anyone reading with an agent. The error codes and the limits are the same across all our APIs, and they are collected in API errors and limits.

Your first call

In the terminal, with the key you create in the dashboard:

curl https://api.lynxmetrics.com/v1/baccarat-1/latest \
  -H "x-api-key: YOUR_KEY"

In Python, with the requests library:

import requests

response = requests.get(
    "https://api.lynxmetrics.com/v1/baccarat-1/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/baccarat-1/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

The yardstick that matters is not "the API is fast", it is how many seconds pass between the hand closing and the data being available. Across the rounds already in our database, the median from settledAt to the round being stored was 3.0 seconds, over 268 checked hands. And the table moves quickly: the median gap between hands was 30 seconds, the shortest 26 seconds, and minutes whenever the table pauses to shuffle or change dealer.

With a 3-second delay on a 30-second hand, you have roughly 27 seconds of slack before the next one: plenty of time to format and publish your message without it landing together with the following hand.

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 Baccarat 1 API costs

PlanPriceFor whomHistoryPer requestPer minuteConnections
ProR$ 21.90 per monthBots and groups7 daysup to 250 rounds60 requests1
BusinessR$ 49.90 per monthSites and larger operationsfullup to 1,000 rounds400 requests5

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 Baccarat 1 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. In an hour the table deals well over a hundred hands, so you can watch the stream work and download a real history before subscribing to anything. 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 bot that posts every hand to your group, cards and score included, reading from /stream.
  • A dashboard or site with the Bead Road and live percentages, drawn straight from the JSON — or simply the live Baccarat 1 table, which is public.
  • A spreadsheet or database with the full history, to study the hands at your own pace.
  • Streak, pair and natural alerts, each one on top of a field that already comes ready.

And if you follow more than one table, the same account covers it: the Lightning Baccarat API answers in the same format, with the same four endpoints, and so does the Bac Bo Live API. A client you wrote for Baccarat 1 works on the others by swapping one piece of the URL.

Frequently asked questions

Is there a free Baccarat 1 API?

You can try LynxMetrics' Baccarat 1 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.

Which table does the Baccarat 1 API follow?

Pragmatic Play's Baccarat 1 table, which is classic baccarat: no multiplier layer and none of the extra Lightning commission. The API delivers the cards, the score, the winner, the pairs and the natural of every hand.

How long after the hand does the result appear in the API?

The measured median is 3 seconds between the hand closing and the data being available, over 268 checked hands. The table deals a hand every 30 seconds at the median, and anyone using the /stream endpoint receives it the moment it is stored.

Which languages can I use with the Baccarat 1 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 Baccarat 1 history go?

To 1 November 2026, when the API went live. Every hand 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 Pragmatic Play or with the casinos that offer Baccarat 1, 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