Magnum 4D APImagnum4d.my ↗
Get the latest Magnum 4D Classic draw result via API: draw number, date, 1st–3rd prizes, 10 special and 10 consolation numbers in one structured response.
What is the Magnum 4D API?
The Magnum 4D API exposes 1 endpoint, get_latest_draw, that returns the most recent Magnum 4D Classic lottery result as a single structured record with 10 response fields. Each response includes the draw number, ISO draw date, weekday abbreviation, first through third prize numbers, arrays of 10 special prize numbers and 10 consolation prize numbers, and an official flag indicating whether the source has marked the result as confirmed.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/430d00da-e3b8-4711-a0e4-b284afa00b35/get_latest_draw' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns the most recent Magnum 4D Classic draw as a single record: the draw number (format NNN/YY), the draw date as ISO YYYY-MM-DD with its weekday abbreviation, the first, second and third prize 4-digit numbers, and the 10 special and 10 consolation 4-digit numbers in the site's published order. All numbers are strings so leading zeros are preserved. One upstream request, no parameters, no pagination. The official flag reports whether the site marks the draw as official.
No input parameters required.
{
"type": "object",
"fields": {
"special": "array of 10 four-digit special prize numbers (strings)",
"draw_day": "three-letter weekday abbreviation of the draw",
"official": "boolean, whether the site marks the draw result as official",
"draw_date": "ISO date YYYY-MM-DD of the draw",
"consolation": "array of 10 four-digit consolation prize numbers (strings)",
"draw_number": "draw identifier string, e.g. one shape is 432/26",
"first_prize": "4-digit first prize number (string)",
"third_prize": "4-digit third prize number (string)",
"second_prize": "4-digit second prize number (string)"
},
"sample": {
"data": {
"special": [
"6129",
"4993",
"8359",
"9890",
"1804",
"8400",
"1428",
"8058",
"8446",
"9869"
],
"draw_day": "WED",
"official": true,
"draw_date": "2026-10-07",
"consolation": [
"6335",
"0327",
"7467",
"8599",
"4258",
"1896",
"5531",
"5539",
"2624",
"7477"
],
"draw_number": "432/26",
"first_prize": "5087",
"third_prize": "8187",
"second_prize": "0254"
},
"status": "success"
}
}About the Magnum 4D API
What the API Returns
The get_latest_draw endpoint returns the most recently published Magnum 4D Classic draw. The response includes draw_number (formatted as NNN/YY, e.g. 432/26), draw_date in ISO 8601 format (YYYY-MM-DD), and draw_day as a three-letter weekday abbreviation. Prize data is split across first_prize, second_prize, and third_prize — each a 4-digit string — plus special and consolation, which are arrays of exactly 10 four-digit strings each.
The official Field
The boolean official field reflects whether the source site has marked the draw as an officially confirmed result. This is useful when polling around draw time: a draw record may appear before all results are finalized, and checking official: true lets you gate downstream processing on confirmation rather than preliminary data.
Coverage and Freshness
The API reflects the latest available draw published on magnum4d.my, which typically runs on Wednesday, Saturday, and Sunday. The endpoint takes no input parameters — it always returns the single most recent draw. There is no pagination or historical lookback in the current endpoint; every call returns the same draw until the next one is published.
The Magnum 4D API is a managed, monitored endpoint for magnum4d.my — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when magnum4d.my changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official magnum4d.my API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display the latest Magnum 4D winning numbers on a lottery results website using
first_prize,second_prize, andthird_prize - Build a result notification bot that checks
official: truebefore sending alerts to subscribers - Populate a mobile app's results screen with the full prize breakdown including all 10
specialand 10consolationnumbers - Log each draw's
draw_numberanddraw_dateto build a local historical archive by polling after each draw schedule - Cross-check user-submitted 4D ticket numbers against the
specialandconsolationarrays for automated prize validation - Show the draw weekday using
draw_dayto help users understand the draw schedule in a results tracker app
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Magnum 4D have an official public developer API?+
What does the `official` field tell me, and when might it be false?+
official boolean reflects whether magnum4d.my has marked that specific draw as a confirmed official result. Draws are held on Wednesday, Saturday, and Sunday evenings, and a record may be retrievable before the site finalizes all prize numbers. If official is false, treat the data as preliminary and poll again before relying on it.Can I retrieve historical draw results or query by draw number?+
get_latest_draw endpoint returns only the single most recent draw and accepts no input parameters, so past draws are not accessible through this endpoint. You can fork the API on Parse and revise it to add a historical or draw-number lookup endpoint.Does the API cover other Magnum game types beyond 4D Classic?+
How should I handle the `special` and `consolation` response fields?+
special and consolation are arrays of exactly 10 strings, each representing a 4-digit prize number. They are returned in the order the source site lists them. Treat each element as a string rather than an integer to preserve any leading zeros that may appear in valid 4-digit numbers.