Skip to content

Lottery API services From lottery data.
To your next feature.

Build a results experience, check a ticket, generate numbers or keep your records up to date. Connect the data through REST, webhooks, a live stream, SDKs or straight from your AI assistant over MCP.

Get API access Explore the documentation

From source to application

Lottevo data

Results · history · updates

REST API

Request → response

Your application

Webhooks

Signed event delivery

Your endpoint

Event stream

An open connection

Your server

Choose the delivery method that fits your product.

More ways to work with lottery data

Check a ticket.
Follow every change.

Go beyond displaying results. Compare selections with past draws, generate numbers, follow jackpot estimates and keep your own records in step—with a clearer view of the data behind them.

Ticket checker

A selection. A history.
A clearer answer.

Check a ticket against recorded draws, including bonus matches and supported digit-game formats. Compare one selection in detail, or send up to 20 tickets together for a summary of each.

EuroMillionsIllustrative match
Your selection
0718243649+0311
Example draw
0718244045+0308
3 main + 1 bonus matchedPrize: unknown

Where prize data and matching rules are available, see what a selection would have won at historical gross amounts, grouped by currency. An unknown prize stays unknown, rather than being treated as a loss.

Build a checking experience

Supported games only. History depends on game format and your access. Historical comparisons do not predict future results.

Jackpot history

See how the estimate moved.

Follow the distinct jackpot figures recorded for an upcoming draw, with currency, observation times and whether an amount is announced, guaranteed or carried over. Build a timeline from the estimates we have collected.

History begins when tracking starts for the game.
Change feed & revisions

Keep your copy in step.

Follow a cursor-based feed of recorded changes instead of repeatedly downloading the same results. Inspect a draw’s corrections with before-and-after values, so your application can update its own records.

Separate a newly published result from a later correction.
Data quality

Understand the coverage behind a result.

See completeness and publication delay over the last 30 days, recalculated every day. Expected, published and missing draws are counted where a fixed schedule allows them to be measured.

Unavailable measurements are explicit—not assumed to be 100%.

Tools on top of the data

Numbers worked out.
Never predicted.

The same history behind your results pages powers three tools for your users: a number generator, reduced systems and statistics that set each game’s draws beside what a fair draw would give.

Number generator

Tickets within your rules.

Valid, distinct tickets for most games in the catalogue, with preferred numbers, ranges and filters read from past draws. A seed repeats the same result, and the response says how many tickets the filters allow.

Reduced systems

More numbers. Fewer tickets.

Play more numbers than a ticket holds and choose a guarantee — if 4 of your numbers are drawn, at least one ticket holds 3 of them — and get the tickets that keep it, far fewer than every combination.

Statistics

The past, measured.

The most and least drawn numbers, the longest absences and how draws are spread — sums, odd and even, high and low, gaps — each beside what a fair draw would give, with a randomness test, over windows from a day to the whole history.

Included in every plan. Statistics describe past draws; neither a filter nor a system changes the chance of winning.

See them in the API reference

Delivery that fits your product

Pull it. Receive it.
Keep it in sync.

Start with the API and add event delivery where it helps. Each method works with your account’s access to games and capabilities.

01

REST API

Request what you need.

Fetch results, explore history and query individual games on your own schedule. Filters and cursor pagination keep imports manageable; ETags help avoid downloading unchanged responses.

Useful for: results pages, archives and scheduled imports.

02

Signed webhooks

Let the update come to you.

Receive events at your HTTPS endpoint when results are published or revised, jackpots change or an expected draw is missed. Verify signatures and inspect delivery attempts from your workspace.

Useful for: notifications and background workflows.

03

Server-Sent Events

Keep a connection open.

Consume an event stream from your server, filter it to the games you follow and resume from the last event after reconnecting. Use the API to load history alongside incoming updates.

Useful for: live dashboards and connected applications.

04

Bulk exports

Take the whole archive at once.

Export the full history of a game as one compressed CSV or NDJSON file. Links are signed and expire, every download is recorded, and the change feed keeps your copy current afterwards. Available on the Enterprise plan.

Useful for: data warehouses, research and first imports.

Webhooks and streaming require the relevant plan and API-key permissions; bulk exports come with the Enterprise plan. Available history and checking support vary by game.

Compare delivery methods

Integrate your way

Your code. Your agent.
Your site.

Beyond plain HTTP: client libraries with a free sandbox key, an MCP server for AI assistants and widgets you embed with one snippet.

SDKs & sandbox

A first result in minutes.

Thin libraries for PHP, JavaScript and Python, and a Postman collection. A free sandbox key reads real EuroMillions results, a week behind, so you can build before you choose a plan.

Read the SDK guide

MCP server

Lottery data for AI assistants.

Connect Claude, Cursor or your own agent to the same results, history, statistics and generator, under your API key and what its plan includes.

Connect over MCP

Widgets

Results on your site, from one snippet.

The latest results and announced jackpots of the games you choose, styled to match your site and sized to their content. Views are counted per plan; from Pro, without the Lottevo mark.

Embed a widget

From an idea to an integration

A clear place to start.

  1. 01

    Choose your games

    Explore the catalogue and check the formats and data available for your target markets.

  2. 02

    Connect your application

    Create an account, try the API with a free sandbox key and choose the delivery method that fits your product.

  3. 03

    Build around the details

    Handle pending prizes, follow corrections and use coverage measurements to give your users the right context.

Take a closer look at our data

Let’s build something useful

Your product.
A world of possibilities.

Whether you’re adding lottery results to an existing website or building something entirely new, start with a clearer view of the data.

Get API accessRead the documentation →