Lottery Numbers API

About the Lottery Numbers API

Pass a supported game identifier—powerball, megamillions, euromillions, or lottomax. The lookup returns the latest drawn numbers, game-specific bonus balls, draw date, and jackpot totals updated daily. EuroMillions draws include Lucky Stars, while Powerball and Mega Millions return their respective special balls. Paid plans can pass a past date for historical drawings, access upcoming draw estimates, and get frequency statistics over the 100 draws up to the returned one: the most and least drawn numbers, the most drawn bonus balls, and how often each number in the draw has come up.

What people use it for

Ticket Verification Portals

Lottery tracking apps compare user-submitted ticket numbers against returned winning numbers and bonus balls to alert players to matching prizes.

News Media Drawboards

When a major draw concludes, regional news outlets display winning numbers and jackpot values on automated result widgets.

Convenience Retail Displays

Broadcast updated winning numbers and current jackpot totals on in-store digital screens to inform lottery customers at the checkout counter.

Office Lottery Syndicates

Pool managers verify group ticket entries against the latest draw dates and winning number arrays to automate weekly payout calculations.

See it in action

The Lottery Numbers API in one live call, from the Playground to your own code.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/lottery

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Optional

1
2

curl "https://api.apiverve.com/v1/lottery?numbers=powerball&date=2024-01-15&stats=true" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/lottery

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117

{
  "status": "ok",
  "error": null,
  "data": {
    "drawDate": "2026-10-26",
    "numbers": [
      18,
      26,
      49,
      50,
      54,
      1
    ],
    "powerball": 1,
    "jackpot": "$691 Million",
    "jackpotValue": 691000000,
    "jackpotFormatted": "$691 Million",
    "lotteryType": "powerball",
    "nextDraw": {
      "drawDate": "2026-10-28",
      "jackpot": "$716 Million",
      "jackpotValue": 716000000,
      "jackpotFormatted": "$716 Million",
      "cashValue": "$307.2 Million",
      "cashValueValue": 307200000
    },
    "stats": {
      "drawsAnalyzed": 100,
      "since": "2026-03-09",
      "hotNumbers": [
        {
          "number": 42,
          "timesDrawn": 13
        },
        {
          "number": 3,
          "timesDrawn": 12
        },
        {
          "number": 64,
          "timesDrawn": 12
        },
        {
          "number": 4,
          "timesDrawn": 11
        },
        {
          "number": 14,
          "timesDrawn": 11
        }
      ],
      "coldNumbers": [
        {
          "number": 1,
          "timesDrawn": 3
        },
        {
          "number": 34,
          "timesDrawn": 3
        },
        {
          "number": 39,
          "timesDrawn": 3
        },
        {
          "number": 62,
          "timesDrawn": 3
        },
        {
          "number": 20,
          "timesDrawn": 4
        }
      ],
      "hotBonusNumbers": [
        {
          "number": 3,
          "timesDrawn": 8
        },
        {
          "number": 14,
          "timesDrawn": 7
        },
        {
          "number": 1,
          "timesDrawn": 6
        }
      ],
      "drawNumbers": [
        {
          "number": 18,
          "timesDrawn": 8,
          "drawsSinceLast": 16
        },
        {
          "number": 26,
          "timesDrawn": 6,
          "drawsSinceLast": 14
        },
        {
          "number": 49,
          "timesDrawn": 8,
          "drawsSinceLast": 12
        },
        {
          "number": 50,
          "timesDrawn": 10,
          "drawsSinceLast": 2
        },
        {
          "number": 54,
          "timesDrawn": 7,
          "drawsSinceLast": 9
        }
      ]
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive Lottery Numbers form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Lottery Numbers API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1Data refreshed daily