Ballpark Pal APIballparkpal.com ↗
Access MLB simulation-based predictions from Ballpark Pal: most likely outcomes across 22 categories, park factors, weather impact, and betting probabilities.
What is the Ballpark Pal API?
The Ballpark Pal API exposes 5 endpoints covering MLB simulation-based prediction data from ballparkpal.com, including the get_most_likely endpoint that returns probability scores and betting lines across 22 statistical categories for batters, pitchers, teams, and games. Response objects include player and team names, matchup details, park and venue identifiers, opponent data, and category-level outcome scores. Park factor and weather endpoints add per-stadium offensive impact ratings and game-level forecast conditions.
curl -X GET 'https://api.parse.bot/scraper/2947b4d9-1c07-4bc2-b79b-0b14a6508e9b/get_most_likely?tab=batters&date=2026-10-09&limit=5&category=1' \ -H 'X-API-Key: $PARSE_API_KEY'
Get most likely MLB outcomes for a given date, optionally filtered by tab (batters/pitchers/teams/games) and/or specific category. Returns player/team names, probabilities, betting prices, matchup details, and more. Without filters, returns all 22 categories (~500 rows). Pagination is not supported; use limit to cap results.
| Param | Type | Description |
|---|---|---|
| tab | string | Filter by tab: 'batters', 'pitchers', 'teams', or 'games'. |
| date | string | Date in YYYY-MM-DD format. Defaults to today's date if omitted. |
| limit | integer | Maximum number of results to return. |
| category | string | Filter by category ID (1-22) or partial name match (e.g. 'HR', 'Quality Start'). Use get_categories endpoint for the full list of IDs and names. |
{
"type": "object",
"fields": {
"date": "string - Display date (e.g. 'June 11, 2026')",
"items": "array of outcome objects with category_id, category_name, team, time, game_id, name, entity_id, park, venue_id, score, opponent, vs_rating, pitcher, pitcher_id, probability, book_price",
"total": "integer - Number of items returned",
"last_updated": "string - Last update time (e.g. '12:57 AM')"
},
"sample": {
"data": {
"date": "June 11, 2026",
"items": [
{
"name": "Corey Seager",
"park": "KC",
"team": "TEX",
"time": null,
"score": null,
"game_id": "824101",
"pitcher": "Wacha",
"opponent": "KC",
"venue_id": "7",
"entity_id": "608369",
"vs_rating": "10",
"book_price": "+233",
"pitcher_id": "608379",
"category_id": "1",
"probability": "30.0%",
"category_name": "Hit a HR"
}
],
"total": 3,
"last_updated": "12:57 AM"
},
"status": "success"
}
}About the Ballpark Pal API
Outcome Predictions
The get_most_likely endpoint is the core of this API. Supply a date in YYYY-MM-DD format and an optional tab parameter (batters, pitchers, teams, or games) to narrow results. You can also filter by category, either as a numeric ID (1–22) or a partial name string like 'HR' or 'Quality Start'. Without filters, the endpoint returns all 22 categories, typically around 500 rows per day. Each result item includes fields such as category_id, category_name, team, name, entity_id, park, venue_id, score, opponent, game_id, and time. Use get_categories to retrieve the static lookup table of all 22 category IDs, names, and their tab groupings before building filter logic.
Park Factors and Weather
get_park_factor_predictions returns per-stadium offensive ratings for a given date, covering how the combination of stadium characteristics and weather forecast affects home run, extra-base hit, single, and run-scoring rates. Each item exposes venue_name, venue_id, outfield_size, altitude, carry, contact_rate, game_time, matchup, and separate fields for combined, stadium-only, and weather-only percentage impacts. Filter by venue_id or category ('hr' or 'runs') to target specific parks or offensive dimensions.
get_weather_predictions returns one entry per scheduled game, showing forecast wind speed and direction, temperature, humidity, atmospheric pressure, and roof status alongside a wind_receptiveness rating. Both park factor and weather endpoints accept game_id and venue_id filters, and venue IDs discovered in one endpoint are reusable in the other.
Date Navigation
get_available_dates resolves the previous_date and next_date strings for programmatic navigation — useful for iterating over a run of dates without hardcoding calendar logic. It also returns the last_updated timestamp, which reflects how recently the simulation data for that day was refreshed. All endpoints default to the current date if date is omitted.
The Ballpark Pal API is a managed, monitored endpoint for ballparkpal.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ballparkpal.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 ballparkpal.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?+
- Build a daily prop-bet dashboard pulling probability scores and betting lines from
get_most_likelyfiltered by thebatterstab - Rank starting pitchers by simulation-predicted outcomes using the
pitcherstab and category filters like 'Quality Start' - Compare park factor offensive impact ratings across all stadiums on a given day to weight DFS roster decisions
- Correlate weather forecast data (wind, temperature, roof status) from
get_weather_predictionswith historical run-scoring outcomes - Automate date iteration with
get_available_datesto backfill or forward-fill prediction records without manual calendar handling - Filter HR park factors by
venue_idto isolate home run friendly parks for same-day power hitter targeting - Cross-reference
venue_idfrom park factor results with weather entries to get a combined stadium-plus-forecast view per game
| 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 Ballpark Pal offer an official developer API?+
What does the `get_most_likely` endpoint return and how do I narrow the results?+
tab parameter to restrict to one of four groups — batters, pitchers, teams, or games — and the category parameter to target a specific category by its numeric ID (1–22) or a partial name like 'HR'. The limit parameter caps the number of rows returned. Call get_categories first to get the full ID-to-name mapping.How fresh is the prediction data, and how do I know when it was last updated?+
last_updated field showing the most recent update time (e.g., '12:57 AM'). Ballpark Pal refreshes its simulations periodically throughout the day, so the timestamp in the response reflects the state of the data at that point. The get_available_dates endpoint also exposes this timestamp if you need to check freshness before fetching full results.