On this page
What this API provides
The product API exposes normalized draw results, lottery metadata, history, customer-visible source confidence, and freshness signals.
Base URL
The product app now serves the same versioned gateway paths under /v1. Production can later point api.lotteryfeedapi.com at this app or a dedicated gateway.
https://api.lotteryfeedapi.com/v1
Response shape
List endpoints return compact bounded collections by default. Use short=1 when you want the request URL to state that the client expects the short public response; compact=1 is kept as a compatibility alias. Use the limit query parameter to cap returned rows; it defaults to 100 and is capped at 1000. Use returned_count, total_count, limit, and has_more to detect when filters matched more rows than the response returned; count remains a backward-compatible alias for returned_count. Draw and catalog rows include stable links to the canonical public page, API docs, and follow-up API endpoints so integrations do not hardcode product URLs. Visual assets, access disclosures, history, and audit-heavy objects stay behind dedicated/internal surfaces so customers do not receive oversized payloads.
{
"generated_at": "2026-05-26T12:00:00Z",
"filters": {},
"count": 1,
"returned_count": 1,
"total_count": 1,
"limit": 100,
"has_more": false,
"data": [
{
"game_code": "md-pick3-midday",
"name": "Maryland Pick 3 Midday",
"state": "Maryland",
"ball_count": 3,
"links": {
"canonical": "/lotteries/md-pick3-midday",
"latest_result": "/lotteries/md-pick3-midday",
"api": "/v1/lotteries/md-pick3-midday",
"api_docs": "/api-docs/lotteries",
"api_integration": "/lotteries/md-pick3-midday/api-integration",
"schedule_api": "/v1/schedules?game_code=md-pick3-midday"
},
"draw_schedule": {
"local_time": "12:27 PM ET",
"utc_time": "16:27 UTC",
"days": "Every day",
"description": "Every day.",
"timezone": "America/New_York"
},
"latest_draw": {
"draw_date": "2026-05-25",
"numbers": ["2", "3", "6"],
"numbers_formatted": "2-3-6",
"numbers_string": "2-3-6",
"source": "mdlottery.com",
"status": "official",
"source_confidence": {
"level": "official",
"label": "Official source",
"policy": "Numbers were published from the official or canonical lottery source path."
},
"provenance": {
"label": "mdlottery.com",
"role": "official",
"source": "mdlottery.com",
"provider": "mdlottery.com",
"display": "mdlottery.com published this result."
},
"links": {
"canonical": "/results/md-pick3-midday/2026-05-25",
"lottery": "/lotteries/md-pick3-midday",
"api": "/v1/results/latest/md-pick3-midday",
"api_docs": "/api-docs/results",
"api_integration": "/lotteries/md-pick3-midday/api-integration",
"schedule_api": "/v1/schedules?game_code=md-pick3-midday&date=2026-05-25",
"history": "/v1/results/history?date=2026-05-25&game_code=md-pick3-midday",
"history_page": "/results/md-pick3-midday/2026-05-25"
}
}
}
]
}Concrete example pages
Use a real number-game page when validating docs, snippets, and search copy. The Maryland Pick 3 Midday lottery page shows the public result view, the result detail page shows the latest winning-number page, the API integration page shows copy-ready requests, and the sandbox docs show deterministic lf_sandbox_* fixtures for CI.
https://lotteryfeedapi.com/lotteries/md-pick3-midday https://lotteryfeedapi.com/results/md-pick3-midday/2026-05-25 https://lotteryfeedapi.com/lotteries/md-pick3-midday/api-integration https://lotteryfeedapi.com/api-docs/sandbox
Endpoints
/v1/results/latestLatest draw rows with stored numbers.
/v1/results/historyHistorical results filtered by date, state, or game.
/v1/lotteriesCustomer-visible lottery catalog with latest numbers.
/v1/schedulesDraw schedule metadata with local time, UTC time, and timezone context.
/v1/statusFeed health and freshness summary.
API documentation FAQ
Short answers for teams using lottery results api in production integrations.
What is the fastest way to test the Lottery Feed API?
Start with /api-docs/quickstart or the API playground, use a server-side bearer key, and request a compact latest-results payload with a bounded limit.
Which response fields should I store first?
Store game_code, draw_date, numbers_formatted, status, source_confidence, and the canonical links. Use game_code plus draw_date as the stable idempotency key for draw upserts.
Which source details are included?
Public responses include compact source-confidence and provenance fields intended for customer integrations.
Next: Quickstart