Equibase APIequibase.com ↗
Access Equibase horse racing data: profiles, race results, track entries, speed figures, and leader stats for horses, jockeys, trainers, and owners.
What is the Equibase API?
The Equibase API covers 10 endpoints for retrieving horse racing data from Equibase.com, including horse profiles with career statistics, race-by-race history, track entries, and exotic wager payoffs. The get_card_results endpoint returns every race on a full card in one call, while get_race_dates lets you discover which tracks have active entries or result charts for a given date without guessing track codes.
curl -X GET 'https://api.parse.bot/scraper/aade7361-953e-4363-895f-0a2b28352de5/search_horse?name=Authentic' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for horses by name. Returns matching horses with reference numbers, sire/dam lineage, year of birth, sex, color, and registry information. Multiple matches are common for popular names; use ref_no from results to fetch full profiles.
| Param | Type | Description |
|---|---|---|
| namerequired | string | Horse name to search for |
| breed_type | string | Breed type filter. Accepted values: TB (Thoroughbred), QH (Quarter Horse). |
{
"type": "object",
"fields": {
"items": "array of horse objects with fields: horseName, refNo, sireName, damName, yob, sex, colorDesc, registry, breedType, areaId"
},
"sample": {
"data": {
"items": [
{
"sex": "H",
"yob": 2017,
"refNo": 10286142,
"areaId": "KY ",
"damName": "Flawless",
"registry": "T",
"sireName": "Into Mischief",
"breedType": "TB",
"colorDesc": "Bay",
"horseName": "Authentic"
}
]
},
"status": "success"
}
}About the Equibase API
Horse Profiles and Past Performances
Use search_horse with a name and optional breed_type (TB or QH) to find horses and retrieve their refNo, sire/dam lineage, year of birth, sex, color, and registry. That refNo feeds into get_horse_profile, which returns yearly career stats (starts, wins, earnings, highest E-Speed figure per year) alongside a history array with each race's track, date, race type, and finish position. get_past_performances goes deeper: for recent races where a chart summary exists, it adds purse, distance, surface, track condition, final time, field size, program number, and the winning horse's name.
Race Cards and Results
get_track_entries returns the full race card for a track/date pair — each race includes race type, purse, distance, surface, post time, and a runners array with program number, post position, horse name, jockey, trainer, weight, morning line odds, and medication flags. For results, get_race_results targets a single race by track code, date, and race_num, returning finishers with Win/Place/Show payoffs plus an exotic payoffs array (wager type, winning numbers, and a parsed numeric payoff amount). get_card_results returns every race on the card in one call with the same shape, saving multiple round-trips.
Track Discovery
get_race_dates is the recommended starting point when you don't know which tracks are active. Pass a date (MM/DD/YYYY) to get all listed tracks for that day, or pass a track abbreviation to see all dates listed for that track. Each record includes has_entries and has_results booleans, the full track_name, and the exact country and track_code values accepted by other endpoints.
Leaders and Speed Figures
get_leaders returns ranked statistics for horses, jockeys, trainers, or owners, filterable by type, breed, and timeframe (year or meet). Each entry includes rank, earnings, starts, win/place/show counts, win percentage, top-three percentage, and earnings per start. get_speed_figures lists E-Speed figure leaders for the current year with the horse's speed figure, earnings, starts, wins, and sire name. get_foals_scheduled gives foal crop stats by year — each entry shows the horse's sire, speed figure, starts, wins, and earnings.
The Equibase API is a managed, monitored endpoint for equibase.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when equibase.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 equibase.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 horse handicapping tool using
get_past_performancesspeed figures, finish positions, and track conditions per race. - Track jockey and trainer standings across a meet using
get_leaderswithtype=jockeyortype=trainerandtimeframe=meet. - Automate daily race card ingestion for a betting app with
get_track_entriesfiltered by track code and date. - Aggregate exotic wager payoffs across all races on a card using
get_card_resultsfor a single track/date request. - Identify top sire lines by cross-referencing
get_speed_figuressireName withget_foals_scheduledsireReferenceNumber. - Discover which tracks have live entries or posted results each morning using
get_race_datesbefore querying other endpoints. - Build a horse search and profile page using
search_horsefor lookup andget_horse_profilefor career stats and race history.
| 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 Equibase have an official developer API?+
What is the difference between `get_horse_profile` and `get_past_performances`?+
get_horse_profile returns yearly aggregate career stats (starts, wins, earnings, highest speed figure per year) plus a race history array with track, date, race type, and finish. get_past_performances returns race-by-race detail including individual speed figures, and for recent races where a chart summary is available it adds purse, distance, surface, track condition, final time, field size, and the winning horse. Both require a ref_no from search_horse.How do I find the correct track code and country code before calling `get_race_results` or `get_track_entries`?+
get_race_dates first. It returns a tracks array where each item includes a track_code, track_name, country, has_entries, and has_results boolean. Pass the same track_code and country values directly to get_race_results, get_track_entries, or get_card_results. Without this step you risk submitting a track abbreviation or country code that yields no results.Does the API return live in-race data such as real-time odds or in-running positions?+
get_track_entries), official result charts, and historical profile data. Real-time tote board odds and live race positions are not currently exposed. You can fork this API on Parse and revise it to add an endpoint targeting live odds data if that surface becomes accessible.Does the API cover international tracks outside the USA and Canada?+
get_race_dates returns a country field and the endpoints accept country codes beyond USA (e.g. CAN, PR), so coverage depends on what Equibase lists. Tracks outside North America that Equibase does not chart are not returned. If you need broader international coverage, you can fork this API on Parse and revise it to target additional data sources.