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 Authentication

API documentation

API Authentication

Production calls use bearer tokens issued from the authenticated API keys page. Tokens must never be exposed in public browser code.

Section

11 / 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.

Bearer token

Send the live API key in the Authorization header from a server-side integration. Store the raw token in a secret manager and rotate it if it is exposed.

curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://api.lotteryfeedapi.com/v1/results/latest?state=MD&ball_count=3&short=1&limit=25"

Test tokens

Reserved lf_sandbox_* tokens are treated as sandbox credentials for public read endpoints. The exact lf_test_demo_sandbox token remains available for legacy examples; arbitrary lf_test_* values are not sandbox credentials. Sandbox tokens are useful for SDK tests and CI smoke checks because they return deterministic fixtures instead of live lottery data. Production integrations should use lf_live_ keys issued to the customer workspace.

Key storage

Raw keys are displayed only when created. Store the token securely, use the visible prefix to identify it later, and revoke or rotate the key from the authenticated account.

Access freshness

A workspace plan can apply a delivery delay after a result is available in the feed. This plan delay is separate from the official publication time, ingestion target, and public page cache refresh interval.

Next: API key scopes
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