Blog · Baccarat 1

Pragmatic Play baccarat API: what exists and what does not

Searching for a Pragmatic Play API lands you in two worlds: the integration for licensed operators and a results API. What each is, and what LynxMetrics delivers.

Published on November 2, 2026 · 6 min read

Anyone searching for a Pragmatic Play API is after one of two very different things, and it pays to separate them first: either the commercial integration, which Pragmatic Play provides to licensed operators under contract so they can run its games on a betting site, or a results API, which delivers what its tables dealt, in JSON, to someone writing a program. LynxMetrics does the second: the Baccarat 1 API delivers every hand from Pragmatic Play's Baccarat 1 table in JSON, with cards, score, winner, pairs and natural, and has stored that history since 1 November 2026.

The two worlds, side by side

Pragmatic Play's integrationLynxMetrics' results API
Who it is forLicensed gaming operators, under contractAnyone with an account and a key
What it doesRuns its games on your site, with wallet and player sessionReads what the table dealt, in JSON
How you get itCommercial negotiation and licensingSign up, confirm your email, open the 2-hour trial
What it deliversThe game itself, to a playerThe round's data, to your program
PriceCommercial, by contractR$ 21.90 or R$ 49.90 per month, per API
How long it takesWeeks or monthsMinutes

Does Pragmatic Play have a public results API?

There is no publicly documented way for a developer to ask Pragmatic Play for a live table's results without being one of its licensed operators. Pragmatic Play's interfaces are business to business, built for whoever is going to offer the games, and the path to them is commercial: licence, contract, wallet integration and certification. None of that helps someone who only wants to read a table's history in a program, which is the problem the LynxMetrics API solves.

Worth saying plainly, because it is the next question: LynxMetrics is not affiliated with Pragmatic Play or with any casino. What we deliver is round data in our own format, and the table's name appears to say where the data comes from.

What LynxMetrics delivers from Baccarat 1

The table is Pragmatic Play's Baccarat 1, classic baccarat, with no multipliers. LynxMetrics follows the table live, hand by hand, and stores the round when it closes. Each 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
  }
}

Each card is a two-letter string: the rank in A23456789TJQK, where T is the ten, and the suit in CDHS — clubs, diamonds, hearts and spades. So "JS" is the jack of spades. Each side's score arrives already computed, from 0 to 9.

The point that matters when you integrate: the format is ours, not Pragmatic Play's. If the source changes something behind the scenes, the JSON reaching your program stays the same, which is why you can write the integration once and forget about it. The same format covers the other baccarat table in the catalogue, Evolution's Lightning Baccarat — the comparison is in Baccarat 1 vs Lightning Baccarat.

What are the Baccarat 1 API endpoints?

Four, all under https://api.lynxmetrics.com/v1/baccarat-1, with your key in the x-api-key header:

EndpointWhat it does
GET /latestThe most recent round
GET /streamHolds the connection open and delivers each round the moment it is stored
GET /resultsPrevious rounds in pages, with limit, before and after
GET /statsCounts, percentages, current streak, pairs and naturals, computed on the spot

The first call is one line:

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

In Python:

import requests

response = requests.get(
    "https://api.lynxmetrics.com/v1/baccarat-1/latest",
    headers={"x-api-key": "YOUR_KEY"},
    timeout=10,
)
round_ = response.json()["data"]
print(round_["outcome"], round_["data"]["player"]["score"], round_["data"]["banker"]["score"])

The full reference, with every parameter, is at Baccarat 1 docs, also in Markdown for anyone reading with an agent, and the overview is in Baccarat 1 API. If you have never integrated an API, start with what an API is.

Why not scrape the table yourself

It is the obvious alternative, and the cost is worth measuring before choosing. Reading a table is something that has to stand 24 hours a day, every day, and that breaks on its own: the source site changes, the session expires, the table switches dealers, the browser reloads. Meanwhile, the rounds that went by do not come back — a live table has no replay. Building it is easy; keeping it alive is what costs. The article scraping or an API does that arithmetic in detail, and storing real-time data covers what to do with the data once it arrives.

What does the Pragmatic Play baccarat API cost on LynxMetrics?

PlanPriceHistoryPer requestPer minuteStream connections
ProR$ 21.90 per month7 daysup to 250 rounds60 requests1
BusinessR$ 49.90 per monthfullup to 1,000 rounds400 requests5

Before paying, the trial is 2 hours with Pro plan limits, no card, repeatable every 24 hours. Since a Baccarat 1 round takes about 30 seconds, two hours of trial are around 240 real hands, enough to look at the actual JSON before deciding. Billing, plan changes and cancellation are covered in how the subscription works.

What you can build with it

  • A Baccarat 1 Telegram bot that posts every hand to your group, with the cards.
  • A dashboard or site with the Bead Road and live percentages, drawn from the JSON.
  • A database or spreadsheet with the history, to study the rounds at your own pace: the path is in Baccarat 1 history.
  • Streak, pair and natural alerts, each one on top of a field that already arrives, with the arithmetic in Baccarat 1 statistics.

And if you only want to watch the table, without writing code, the live Baccarat 1 results are open on the site, no account needed.

Frequently asked questions

Does Pragmatic Play have a public API for live table results?

There is no publicly documented way for a developer to ask Pragmatic Play for a live table's results. Its interfaces are business to business, for licensed operators that will offer the games, and the path to them is commercial. To simply read what the table dealt, the LynxMetrics Baccarat 1 API delivers every hand in JSON.

Is LynxMetrics affiliated with Pragmatic Play?

No. LynxMetrics is not affiliated with Pragmatic Play or with any casino. Round data is delivered in LynxMetrics' own format, and the table's name appears only to say where the data comes from.

What does each Baccarat 1 API round contain?

The round's fixed identifier, the start and end in UTC, who won (player, banker or tie), each side's cards in the order they came out, each side's score from 0 to 9, whether each side made a pair and whether the hand ended in a natural.

What does the Pragmatic Play Baccarat 1 API cost?

The Pro plan is R$ 21.90 per month, with 7 days of history, up to 250 rounds per request, 60 requests per minute and 1 stream connection. Business is R$ 49.90 per month, with full history, up to 1,000 rounds per request, 400 requests per minute and 5 connections.

Do I need a licence or a contract to use the API?

No. You create an account, confirm your email and open the 2-hour trial in the dashboard, which uses Pro plan limits and asks for no card. The subscription is monthly, per API, and each project has its own keys.

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