Skip to content
Lottery Feed API

Lottery Feed API

ResultsPersonalAPI DocsPricingContact
Sign inJoin the Free Beta
  1. Home
  2. /
  3. API docs
  4. /

  5. API Playground

API documentation

API Playground

Run live requests against the product gateway and inspect the exact JSON returned to customer integrations.

Section

07 / 27

OpenAPI JSON
01Introduction02Quickstart03Polling and integration04Sandbox fixtures05SDK starter06Embeddable widgets07API playground08OpenAPI spec09Postman collection10API changelog11Authentication12API key scopes13Freshness levels14Source confidence15Status monitoring16Rate limiting17Get countries18Get states19Get lotteries20Get lottery21Get schedules22Draw years23Lottery results24History export25Number frequency26Result checker27Error handling

Live API examples

Jump from the docs to real public pages that use the same read models.

Latest results browserSee the compact public result model with filters and draw dates.
Lottery catalogFind game names, states, ball counts, latest numbers, and API guides.
Maryland Pick 3 API guideOpen a concrete endpoint example using the same game shown in snippets.
Pricing and limitsCompare freshness targets, request limits, and integration features.
Customer integration centerSign in to check API keys, usage, webhook delivery, plan limits, and the next recommended action.
OpenAPI contractUse the machine-readable contract for code generation and integration tests.
Live gateway

Test the same JSON your integration will call.

Requests run from this browser against the product /v1 gateway. Bearer tokens stay in current component state and are not written into the page URL or browser storage.

Current preset

History by date

GET

Daily archive rows for a date, optionally narrowed to state or game.

State
Ball count
Game code
Draw date
Limit

Caps list payloads. API maximum is 1000.

Adds the bounded public source-confidence timeline. Default responses stay compact.

Bearer token

Use a server-side lf_live or lf_test key. The value stays in browser memory for this playground session.

Env var is safest for shared docs. Inline mode is only for copying a local smoke-test command from this browser session.

Request

GET /v1/results/history?date=2026-08-14&state=MD&ball_count=3&game_code=md-pick3-midday&limit=25&short=1
No key prefix selected
Paste token to run live requests
Snippet uses LOTTERY_FEED_API_KEY

Account links can preselect a key prefix. Shared snippets should keep the token in a server-side LOTTERY_FEED_API_KEY environment variable.

curl -sS -X GET 'https://lotteryfeedapi.com/v1/results/history?date=2026-08-14&state=MD&ball_count=3&game_code=md-pick3-midday&limit=25&short=1' \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer $LOTTERY_FEED_API_KEY'

Response

Compact customer-facing JSON, not raw upstream payloads.

Run a request to inspect the live response.

Use the filters on the left to keep payloads bounded.

How to use it

Choose an endpoint preset, narrow the request with state, ball count, date, or game code, then run it against the same /v1 routes documented here.

Token handling

When API auth is enabled, paste a bearer token into the local field. The token is kept in browser state only and is not copied into the URL or stored by this page.

Next: OpenAPI spec
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 resultCompanyTermsPrivacyAccount