Lottery Numbers is a simple tool for looking up winning lottery numbers. It returns the winning lottery numbers based on the lottery name provided. Supports Powerball, Mega Millions, EuroMillions, and Canada Lotto Max with historical data lookup.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Lottery Numbers response payload
}
}
About the Lottery Numbers API
Lottery Numbers works by analyzing the lottery name provided and looking up the winning numbers. It uses various sources to lookup the winning numbers based on the lottery name and returns the winning lottery numbers. You can also lookup historical winning numbers by providing an optional date parameter.
What people use it for
- Lottery Results
- Use the Lottery Numbers API to lookup winning lottery numbers for lottery results. Use the data to check winning numbers, verify tickets, and claim prizes
- Historical Analysis
- Lookup historical winning lottery numbers by providing a date. The API returns the nearest draw to the specified date
- Data Analysis
- Use the Lottery Numbers API to lookup winning lottery numbers for data analysis. Use the data to study patterns, identify anomalies, and draw insights
- Research & Analysis
- Lookup winning lottery numbers by using the Lottery Numbers API for research and analysis. Use the data to study trends, conduct studies, and make informed decisions
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
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Lottery Numbers
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Lottery Numbers API do?
How do I authenticate Lottery Numbers API requests?
How much does the Lottery Numbers API cost?
How fast is the Lottery Numbers API?
What response formats does the Lottery Numbers API support?
What HTTP method does the Lottery Numbers API use?
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
| Parameter | Type | Example | Description |
|---|---|---|---|
numbersRequired | string | powerball | The lottery game to lookup: powerball, megamillions, euromillions, or lottomaxpowerballmegamillionseuromillionslottomax |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
dateOptionalPremium | string | 2024-01-15 | Optional date for historical lookup (YYYY-MM-DD). Returns the nearest draw to this date. date |
curl "https://api.apiverve.com/v1/lottery?numbers=powerball&date=2024-01-15" \
-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.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
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.
{
"status": "ok",
"error": null,
"data": {
"lotteryType": "megamillions",
"drawDate": "2026-02-04",
"numbers": [
10,
50,
55,
58,
59,
5
],
"megaBall": 5,
"jackpot": "$70 Million",
"jackpotValue": 70000000,
"jackpotFormatted": "$70 Million",
"nextDraw": {
"drawDate": "2026-02-07",
"jackpot": "$82 Million",
"jackpotValue": 82000000,
"cashValue": "$37.2 Million",
"cashValueValue": 37200000
}
}
}
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.
| Field | Type | Example | Description |
|---|---|---|---|
lotteryType | string | "megamillions" | |
drawDate | string | "2026-02-04" | Date of the drawing |
numbers | array | [10, ...] | Array of winning main numbers |
megaBall | number | 5 | |
jackpot | string | "$70 Million" | Jackpot amount for this drawing |
jackpotValue | number | 70000000 | |
jackpotFormatted | string | "$70 Million" | |
nextDrawPremium | object | {...} | Estimated details for the upcoming, not-yet-drawn draw. Absent for a short window after each draw, while the operator recalculates the estimate |
drawDatePremium | string | "2026-02-07" | Date of the upcoming draw (best-effort; may be null when the source lists it only as a relative time) |
jackpotPremium | string | "$82 Million" | Estimated jackpot for the upcoming draw |
jackpotValuePremium | number | 82000000 | Estimated jackpot for the upcoming draw as a numeric value |
cashValuePremium | string | "$37.2 Million" | Estimated cash (lump-sum) value for the upcoming draw. Powerball and Mega Millions only |
cashValueValuePremium | number | 37200000 | Estimated cash value for the upcoming draw as a numeric value. Powerball and Mega Millions only |
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.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
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.
| Plan | Per month | Credits | Lottery Numbers calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
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.
Call it from cURL — GET /v1/lottery
No SDK to install — this is a plain HTTPS call to /v1/lottery with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/lottery" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/lottery
Install the Node.js SDK, then call the Lottery Numbers API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/lotteryconst res = await fetch("https://api.apiverve.com/v1/lottery", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/lottery
No SDK to install — this is a plain HTTPS call to /v1/lottery with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/lottery",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/lottery
Install the C# / .NET SDK, then call the Lottery Numbers API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.LotteryNumbersusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/lottery");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/lottery
No SDK to install — this is a plain HTTPS call to /v1/lottery with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/lottery", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/lottery
No SDK to install — this is a plain HTTPS call to /v1/lottery with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/lottery");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/lottery
No SDK to install — this is a plain HTTPS call to /v1/lottery with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/lottery")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
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.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Lottery Numbers API.
Data Lookup
- ASN Lookup
- Bible
- Country Calling Code
- Dictionary
- Dog Breeds
- Emoji Lookup
- Gender Detector
- Gravatar Lookup
- IP Demographics
- Lottery Numbers
- Nobel Prizes
- Open Source Licenses
- Thesaurus
- Timezone Lookup
- Unicode Character Lookup
- World Time
- ZIP Demographics
Related articles
All articles →
The Timezone Bug That Cost Us a ClientA scheduled email went out at 3 AM instead of 9 AM. The client wasn't happy. Here's what went wrong.Read
Build a Lead Enrichment Pipeline That Actually WorksTurn email addresses into full customer profiles. Location, company, social links—automatically. Here's how to build it.Read
Weather APIs: Build a Dashboard That's Actually UsefulCurrent conditions, forecasts, air quality, sunrise times—here's how to build a weather dashboard users will love.Read