US Lottery Draw Results — Powerball & Mega Millions

Collect published draw observations from two New York State Gaming Commission datasets. Export numbers, bonus balls, optional multipliers and Double Play fields with the original source values and observation timestamp. Useful for lottery results pages, dataset reconciliation and research pipelines.

Independent tool using public feeds; no regulator or lottery affiliation. Results are not certified tickets, payout records, winning-number predictions or advice on choosing bets. Historical number matrices have changed: validation checks structure and dates, without certifying every historical rule era.

Quick start

Choose one or both games, set an inclusive date range if needed, and optionally set Max total charge under run options to bound paid delivery. In API calls this is maxTotalChargeUsd. Allow at least 90 seconds and 512 MB. The form example returns up to five newest observations per game:

{
  "games": ["powerball", "megamillions"],
  "maxDrawsPerGame": 5
}

With no INPUT record or {}, both games are selected, dates run from 30 calendar dates before today UTC through today, inclusive, and the maximum is 100 per game. This is a date query, not a promise that a draw occurred on every date. Future date bounds do not produce predictions.

Input	Meaning
games	powerball, megamillions, or both; no duplicate values
dateFrom	Inclusive YYYY-MM-DD; default is today minus 30 calendar days in UTC
dateTo	Inclusive YYYY-MM-DD; default is today UTC
maxDrawsPerGame	Integer 1–1000; default 100, form example 5

Powerball's feed starts on 2010-02-03 and Mega Millions on 2002-05-17. A selected range must not begin before the history of any selected game. Both games use the same range. To retrieve older Mega Millions history, select that game alone. Unknown input fields and invalid dates are rejected.

Results

The default Dataset contains two record types. Filter recordType=lottery_draw for billable observations. recordType=diagnostic describes source or budget limitations and requests no result event.

Draw field	Meaning
id, game, drawDate	Stable game/date identity and the source's draw date
numbers, bonusBall	Five main numbers in source order and the separate bonus ball
multiplier	Optional published multiplier; null when not supplied
doublePlayNumbers, doublePlayBonusBall	Optional Powerball Double Play values; null when not supplied
contentDigest	SHA-256 of normalized facts; excludes observation time, so feed revisions can be detected
validation	structural_not_rules_era_certification
source	Dataset ID, publisher, exact draw-query URL, observation time and raw date/number fields
billing	Whether this row requested a result event; settlement is unconfirmed at the instant of writing

source includes rawDrawDate, rawWinningNumbers, rawBonusBall, rawMultiplier and rawDoublePlayWinningNumbers. Missing optional fields remain null. The digest is a consistency key, not an authenticity signature. Save the Dataset in your own workflow if you want a historical archive or comparisons; this version does not maintain cross-run state.

Rows are grouped by game alphabetically (megamillions then powerball), with newest draws first within each game. Under a tight run budget the earlier game can consume the allowance first. Run the games separately when you need independent budgets.

OUTPUT in the default key-value store is a summary containing counts, configuration and per-game coverage. It contains no draw records. When present, check these fields:

• sourceComplete: all selected queries returned successfully without hitting the result cap. It does not prove that every scheduled draw is present in the publisher's dataset.
• deliveryComplete: all collected observations were delivered and their result events verified. Source completeness is separate.
• coverage[].rangeComplete and hasMore: whether one lookahead row showed truncation; older draws are omitted when truncated.
• coverage[].status: read or failed. A successful empty date query is distinct from a failed source.

confirmedResultEvents counts events confirmed by this process; compare with the settled run counters during recovery. datasetWritesAcknowledged includes acknowledged diagnostic writes as well as draw rows. deliveryUncertain flags a write/charge uncertainty when available; a failed run may have no saved summary. A successful source response truncated by the configured maximum is reported as SOURCE_TRUNCATED; SOURCE_PARTIAL means at least one selected source failed.

One failed game does not discard valid observations from the other. Duplicate, out-of-range, malformed or unordered records reject that game's response atomically. If no usable observations are obtained and any source fails, the run fails with SOURCE_UNAVAILABLE. A valid empty query succeeds with zero result events. Truncated or partly unavailable output ends with a visible partial status.

Pricing and recovery

The active price shown in Apify applies. One result-found event is requested per delivered draw, including repeated observations in later runs and valid observations from a partial run. A platform start charge may also apply. Diagnostics do not request result events; this does not eliminate the start charge. No separate default-Dataset-item fee is supported by this version.

Optionally set Max total charge to bound paid delivery. A verified unset limit permits delivery within the source and size bounds. An explicit zero prevents paid rows. Unreadable or inconsistent run-limit settings stop before paid delivery with BUDGET_UNREADABLE. An insufficient finite limit yields budget_stopped and no further paid rows. The program uses exact decimal comparisons and verifies the named event count after each delivery.

A failed write or uncertain charge is not automatically retried. Inspect the Dataset and settled run counters before starting another run: delivered rows or charges can exist even if OUTPUT is missing after a late failure. The Dataset's unconfirmed_at_write label is intentional; it is not the final settlement receipt. A durable same-run claim prevents automatic replay after a restarted container; this version does not resume interrupted work or claim migration recovery. A new run can legitimately retrieve and charge for the same observations again.

Sources and limits

• Official Powerball draw feed
• Official Mega Millions draw feed

Fixed public HTTPS sources only, no credentials, caller URLs or redirects. Each request has a 20-second timeout and a 2 MiB decoded response limit. Up to 1001 source records per game are read to return at most 1000. There are no automatic source retries. The full collector result and summary each have a local 4 MiB limit; this is a product limit, not a statement about Apify's storage capacity.

Feed publication delays, corrections or source outages are possible. A successful query is not an independently certified draw calendar, payout or jackpot record. No probability estimates, odds optimization or jackpot amount is supplied.