Skip to content
Lottery Feed API

Lottery Feed API

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

  3. Results

0 available history rows

No public lottery results for August 6, 2026 yet.

No customer-visible winning-number rows are stored for this date yet. Use latest results or choose another available date.

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.

Results API docsBrowse lottery profiles

August 6, 2026

Selected date

0

Visible rows

0 / 20 numbered rows

Result availability

F1

Access

Filter history results

The selected draw date reads the stored history snapshot, then filters by state, ball count, status, or lottery name.

0 shown
Search
Draw date
State
Ball count
Status

Active filters

Customer-visible result filters for this view.

Draw date: 2026-08-06

Stored archive dates

SEO-safe history

Recent stored history snapshots with customer-visible winning numbers.

No stored public history for this date yet.

The archive has no customer-visible rows for this draw date. Try the latest result browser or another recent archive date.

API request and result quality

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

Customer API request

This request returns rows for draw_date=2026-08-06. The copied cURL uses the compact public JSON contract and a bounded limit.

curl -sS 'https://api.lotteryfeedapi.com/v1/results/history?date=2026-08-06&short=1&limit=60' \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY'
GET /v1/results/history?date=2026-08-06&short=1&limit=60Open in API playground
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

Selected date archive quality

2026-08-06

This date is not yet available in the stored public archive.

Archive

No stored snapshot yet

Available rows

0

Last updated

Not available yet

Selected date

2026-08-06

Result availability

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

Visible numbers

0 / 20 numbered rows

Access timing

No F1 delay rows

Results API FAQ

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

How do I request the 2026-08-06 history view through the API?

Use GET /v1/results/history?date=2026-08-06&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 date=2026-08-06. 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 2026-08-06 history view show fewer rows than expected?

No rows are currently hidden by the F1 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