Stats24 APIstats24.com ↗
Access football draw predictions from stats24.com via a single API endpoint. Filter by date to retrieve match-level draw market forecasts across competitions.
What is the Stats24 API?
The stats24.com API exposes 1 endpoint — get_draw_matches — that returns football match predictions filtered to draw markets (Draw In Final Result, Draw In First Half). Each response includes the selected date, an array of individual match predictions, the total prediction count for that date across all markets, and a dedicated count of draw-specific predictions. Pass a date in DD-MM-YYYY format or omit it to retrieve today's predictions.
curl -X GET 'https://api.parse.bot/scraper/be2c30e0-dc08-4ac3-811e-41be2ebb5272/get_draw_matches?date=13-09-2026' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns football matches that stats24.com predicts to end in a draw, across both draw markets the site publishes: Draw In Final Result (market_id 16) and Draw In First Half (market_id 15). Grain is one row per match per draw market, so a match predicted as a draw in both markets appears twice with different market_id values. Each row carries the site's prediction confidence percentage (prediction_value, with the home/away components), the bookmaker odds as a string (empty string when the site lists no odds), league/country/contest identifiers, and match date (DD/MM/YYYY) and kick-off time. Without a date, the site's current day is used (date in the response is the site's selected day). With a date in DD-MM-YYYY form, that day's predictions are returned, including finished matches for past days; the site's own future-day availability determines whether later dates have rows. total_predictions counts all match predictions the site lists for that day across every market, not just draws. A call for the site's current day costs three page loads; another day costs several more requests (the site's draw lists for other days come from its data feed). An invalid date is rejected with a stale_input error. No pagination: the full day is returned in one response.
| Param | Type | Description |
|---|---|---|
| date | string | Day to fetch in DD-MM-YYYY format (one shape: 13-09-2026). Must be a real calendar date. When omitted, the site's current day is used. |
{
"type": "object",
"fields": {
"date": "Selected day in DD-MM-YYYY format",
"draw_matches": "Array of draw predictions, one row per match per draw market",
"total_predictions": "Number of match predictions the site lists for the day across all markets (not only draws)",
"draw_matches_count": "Number of rows in draw_matches",
"draw_matches[].odds": "Bookmaker decimal odds as a string; empty string when the site lists none",
"draw_matches[].match_id": "Site match identifier (integer); the same match can appear once per draw market",
"draw_matches[].bookmaker": "Bookmaker name; empty string when no odds are listed",
"draw_matches[].market_id": "Draw market identifier: 16 = Draw In Final Result, 15 = Draw In First Half",
"draw_matches[].match_date": "Match date in DD/MM/YYYY format (may differ from the selected day for late-night kick-offs)",
"draw_matches[].match_time": "Kick-off time HH:MM as shown by the site",
"draw_matches[].league_name": "League name with league_id, country_name/country_id and contest_group_id/contest_group_name identifying the competition stage",
"draw_matches[].market_name": "Draw market label as the site shows it",
"draw_matches[].prediction_value": "Site prediction confidence percentage for the draw market (number)",
"draw_matches[].away_prediction_value": "Away-team component of the prediction percentage (number)",
"draw_matches[].home_prediction_value": "Home-team component of the prediction percentage (number)"
},
"sample": {
"data": {
"date": "14-09-2026",
"draw_matches": [
{
"odds": "4.50",
"match_id": 3303369,
"away_team": "Estoril",
"bookmaker": "Betway",
"home_team": "Sporting Braga",
"league_id": 172,
"market_id": 16,
"country_id": 176,
"match_date": "14/09/2026",
"match_time": "19:45",
"sport_name": "Football",
"league_name": "Portuguese Liga",
"market_name": "Draw In Final Result",
"away_team_id": 3477,
"bookmaker_id": "1",
"country_name": "Portugal",
"home_team_id": 3479,
"contest_group_id": 78134,
"prediction_value": 63,
"contest_group_name": "Liga Portugal",
"away_prediction_value": 50,
"home_prediction_value": 75
},
{
"odds": "",
"match_id": 3308572,
"away_team": "Neftekhimik",
"bookmaker": "",
"home_team": "Spartak Kostroma",
"league_id": 180,
"market_id": 15,
"country_id": 182,
"match_date": "14/09/2026",
"match_time": "15:00",
"sport_name": "Football",
"league_name": "First League",
"market_name": "Draw In First Half",
"away_team_id": 4989,
"bookmaker_id": "",
"country_name": "Russia",
"home_team_id": 5008,
"contest_group_id": 78102,
"prediction_value": 68,
"contest_group_name": "First League",
"away_prediction_value": 60,
"home_prediction_value": 75
}
],
"total_predictions": 149,
"draw_matches_count": 21
},
"status": "success"
}
}About the Stats24 API
What the API Returns
The get_draw_matches endpoint returns a structured snapshot of stats24.com's football predictions for a given date, narrowed to matches where the predicted market is draw-type. The response carries four top-level fields: date (the queried date in DD-MM-YYYY format), draw_matches (an array of individual match prediction objects), draw_matches_count (how many matches carry a draw market prediction), and total_predictions (the full count of predictions the site has published for that date across all market types — useful for understanding how draw predictions sit relative to the broader prediction schedule).
The date Parameter
The single optional input is date, passed as a string in DD-MM-YYYY format — for example, 03-09-2026. When omitted, the endpoint defaults to today's date. Data availability is tied to stats24.com's own prediction schedule, so some dates may return fewer or no draw predictions depending on fixture density and site coverage.
Draw Market Types
The draw_matches array filters specifically for two market labels: Draw In Final Result and Draw In First Half. This means only matches where the site's prediction falls into one of these two categories appear in the response. Matches predicted for other outcomes — home win, away win, over/under goals, etc. — are excluded from the draw_matches array, though they are counted in total_predictions.
The Stats24 API is a managed, monitored endpoint for stats24.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when stats24.com 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 stats24.com 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?+
- Track daily draw predictions across football competitions using the
dateparameter to build a historical dataset - Compare
draw_matches_countagainsttotal_predictionsto measure the proportion of draw forecasts on any given day - Filter the
draw_matchesarray for first-half draw predictions specifically to separate short-horizon forecasts from full-match draws - Feed draw prediction data into a sports analytics dashboard to monitor forecast consistency over time
- Automate a daily digest of draw-predicted fixtures by scheduling calls with no
dateargument to always fetch today's data - Cross-reference draw predictions with match results to back-test stats24.com's prediction accuracy for draw markets
| 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 stats24.com have an official developer API?+
What does `total_predictions` represent versus `draw_matches_count`?+
total_predictions reflects all match predictions stats24.com has published for the queried date across every market type — not just draw markets. draw_matches_count is the subset of those where the predicted market is either Draw In Final Result or Draw In First Half. The difference between the two tells you how many predictions on that date are for non-draw outcomes.Are predictions available for past dates or only today?+
date parameter accepts any DD-MM-YYYY value, so you can query past dates as well as today. However, data availability depends on stats24.com's own publishing schedule. Dates with no published predictions — or dates outside the site's historical archive — may return empty or minimal results.Does the API return predictions for non-draw markets like home win, away win, or over/under goals?+
total_predictions field shows how many predictions exist across all markets on a given date, but only draw-typed entries appear in draw_matches. You can fork this API on Parse and revise it to add endpoints for other market types.