Skip to content
Lottery Feed API

Lottery Feed API

ResultsPersonalAPI DocsPricingContact
Sign inJoin the Free Beta
  1. Home
  2. /
  3. Results

14 available result rows

Latest lottery results, ready for API customers.

Browse the same compact latest-result fields exposed through the API: numbers, draw date, lottery name, and jurisdiction. Rows without validated numbers are not shown.

Public demo — 24h delivery delay. This is an access policy, not an ingestion target. If an official lottery source delays publication, including during major jackpot events or additional validation processes, the feed can only publish after the official result becomes available.

170 results are hidden by the public-demo access delay for this view.

Results API docsBrowse lottery profiles

14

Visible result rows

0

Official rows in view

3

Jurisdictions in view

public-demo

Access

Filter latest results

Use the same fields customers care about on the public site: state, ball count, status, lottery name, or date.

0 shown
Search
Draw date
State
Ball count
Status

Active filters

Customer-visible result filters for this view.

State: OK

Stored archive dates

SEO-safe history

Recent stored history snapshots with customer-visible winning numbers.

No lottery results match these filters.

Try a state name, abbreviation, lottery name, draw period, ball count, or a shorter search phrase.

API request and result quality

Open the compact API example and selected-date archive evidence.

Customer API request

Latest requests return each result date in latest_draw.draw_date / draw_date. The copied cURL uses the compact public JSON contract and a bounded limit.

curl -sS 'https://api.lotteryfeedapi.com/v1/results/latest?state=OK&short=1&limit=60' \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY'
GET /v1/results/latest?state=OK&short=1&limit=60Open in API playground

Result availability

Customer-visible numbers and access timing for the current result view.

Lottery Feed API

Normalized lottery draw results, history, schedules, source-confidence metadata, and descriptive analytics for integrations and personal analysis.

Independent software and data service. We do not sell lottery tickets, accept bets or player funds, operate draws, determine outcomes or pay prizes.Lottery names and trademarks belong to their respective owners. Lottery Feed API is an independent data service and is not affiliated with, endorsed by, sponsored by or operated by any lottery authority.
LotteriesDaily ArchiveCountriesStatesStatusResponsible UseAcceptable UseReport incorrect result

Visible numbers

0 numbered rows

Access timing

170 delayed by public-demo

Results API FAQ

Practical notes for turning this result browser into a compact server-side API request.

How do I request the latest results view through the API?

Use GET /v1/results/latest?state=OK&short=1&limit=60 from a server-side integration. This page currently shows 0 visible rows. The response is a compact JSON read model with lottery name, state, draw date, numbers, status, source confidence, and access metadata. Do not expose bearer API keys in browser code.

Which filters are API-compatible?

This API request includes state=OK. Supported API filters on this page are date for history, state, ball_count, game_code, and q/search text. The page can filter by status for browsing, while API responses return row status as data instead of accepting status as a request filter.

Why can the latest results view show fewer rows than expected?

170 rows are currently hidden by the public-demo access delay for this view. Public pages and API responses also omit rows without customer-visible winning numbers so operator gaps and unpublished draws do not pollute customer payloads.

Can filtered results pages be indexed?

Latest results and high-quality date history pages can be indexed when they contain enough visible numbers. Search, state, ball-count, status, and pagination URLs stay noindex and canonicalize back to the latest or selected date page to avoid thin duplicate result pages.

Company
Terms
Privacy
Account