API documentation

Lottery Results Checker

Checks a customer number set against a stored draw result.

Section

26 / 27

OpenAPI JSON

Live API examples

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

Checker overviewRead the public integration overview with match classes and copy-ready request/response examples.

Try the API playgroundExercise compact result endpoints before wiring the checker into a backend.

Maryland Pick 3 integration guideUse a concrete lottery guide for request examples and server-side key handling.

Maryland Pick 3 result pageCompare checker output against the customer-visible stored draw.

OpenAPI checker contractValidate request bounds and response fields from the machine-readable spec.

Responsible data use

Result checks classify stored winning numbers only. They do not determine prizes, payouts, eligibility, or jurisdiction-specific play outcomes.

Lottery Feed API is a data/API service, not a gambling operator. Public pages and customer integrations should show age/legal requirements where applicable and should not present historical statistics as a way to improve winning odds.

U.S. problem-gambling help resources are available from the National Council on Problem Gambling. Use jurisdiction-specific help links where local rules require them.

Request

Use POST for checks so longer number sets and future options do not leak into logs as query strings. The submitted numbers array is bounded to 20 entries and each token is bounded to 16 characters so malformed client payloads fail before any feed-history lookup.

POST https://api.lotteryfeedapi.com/v1/results/check
Authorization: Bearer YOUR_API_KEY

{
  "game_code": "md-pick3-midday",
  "draw_date": "2026-05-25",
  "numbers": ["6", "2", "3"]
}

Response

The checker reports exact-position matches, any-order number matches, and a match class. It does not estimate prizes or payouts because those require jurisdiction-specific play-type rules.

{
  "matched": true,
  "match_count": 3,
  "number_match_count": 3,
  "match_class": "exact_order",
  "match_summary": "Submitted numbers match the stored winning numbers in exact order.",
  "disclaimer": "Result checks classify stored numbers only. Prize or payout rules require jurisdiction-specific verification.",
  "game_code": "md-pick3-midday",
  "draw_date": "2026-05-25",
  "submitted_numbers": ["6", "2", "3"],
  "submitted_numbers_formatted": "6-2-3",
  "winning_numbers": ["6", "2", "3"],
  "winning_numbers_formatted": "6-2-3"
}

Responsible use

Result checks classify stored numbers only. They are not payout determinations, player eligibility checks, or legal lottery-operator decisions. Customer products should use official lottery rules for prizes and local legal disclosures before displaying any prize-related outcome.

Match classes

Use match_class for customer-facing logic: exact_order: Every submitted number matches the stored draw in the same position. all_numbers_any_order: The submitted set contains the same numbers, but not in the same order. partial_position: At least one number matches in the same position. partial_numbers: At least one number appears in the stored draw, but not in the same position. no_match: The stored draw is visible and no submitted numbers match. no_visible_draw: The requested draw is unavailable for the caller, date, game, or freshness level.

Next: Error handling