equibase.com APIequibase.com ↗
Access Equibase horse profiles, race results, track entries, speed figures, and leader stats for jockeys, trainers, and owners via a structured JSON API.
curl -X GET 'https://api.parse.bot/scraper/aade7361-953e-4363-895f-0a2b28352de5/search_horse?name=Authentic&breed_type=TB' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for a horse by name to retrieve its reference number and basic details including sire, dam, year of birth, and registry information.
| 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": {
"data": "array of horse objects with fields: horseName, refNo, sireName, damName, yob, sex, colorDesc, registry, breedType, areaId"
},
"sample": {
"data": [
{
"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.com API
This API exposes 7 endpoints covering Equibase.com horse racing data, from searching horses by name to retrieving career statistics, historical race results, and track entries. The get_leaders endpoint returns paginated rankings with earnings, starts, and win/place/show counts for horses, jockeys, trainers, and owners. Each endpoint returns structured JSON suitable for building handicapping tools, form guides, or racing analytics pipelines.
Horse Search and Profiles
The search_horse endpoint accepts a horse name and an optional breed_type filter (TB for Thoroughbred, QH for Quarter Horse), returning an array of matches. Each result includes horseName, refNo, sireName, damName, yob, sex, colorDesc, registry, breedType, and areaId. The refNo from search results is the key input for get_horse_profile, which returns full career statistics and historical race records including E-Speed figures for a specific horse.
Race Results and Track Entries
get_race_results takes a date (MM/DD/YYYY), a track abbreviation (e.g., AQU), an optional country code, and a race_num to return finishing positions and payoffs for a single race. get_track_entries uses the same date, track, and country inputs to return post times and entry labels for all races at a track on a given day — useful for building pre-race dashboards or monitoring upcoming cards.
Leaders and Speed Figures
The get_leaders endpoint supports filtering by type (horse, jockey, trainer, owner), breed (TB or QH), and timeframe (year or meet). Response fields include earnings, rank, starts, and win/place/show counts, along with the entity name appropriate to the type queried. Results are paginated with a total_rows count. get_speed_figures returns E-Speed figure leaders for performance comparison. get_foals_scheduled exposes upcoming stakes nominations and registered foal lists with no required inputs.
Coverage and Data Freshness
Track abbreviations follow Equibase's standard codes (e.g., AQU for Aqueduct). Dates must be formatted as MM/DD/YYYY across all endpoints that accept them. The breed_type filter is consistent across search and leader endpoints, making it straightforward to scope queries to Thoroughbred or Quarter Horse circuits independently.
- Build a handicapping tool that pulls career stats and E-Speed figures for horses entered in an upcoming race.
- Track yearly earnings leaders by jockey or trainer across Thoroughbred and Quarter Horse circuits.
- Aggregate historical race result payoffs by track to analyze exotic betting trends.
- Monitor daily track entries and post times for a specific track to power a racing calendar.
- Cross-reference foal nominations with stakes race schedules for bloodstock research.
- Rank trainers by meet-level win percentage using starts and win counts from
get_leaders. - Compile sire and dam lineage data from
search_horseresults for pedigree analysis.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Equibase have an official developer API?+
What does `get_leaders` return, and can I filter by both breed and timeframe together?+
get_leaders accepts type (horse, jockey, trainer, owner), breed (TB or QH), and timeframe (year or meet) as independent optional filters that can be combined. The response includes earnings, rank, starts, and win/place/show counts, plus a total_rows field for pagination. The name field in each stat object varies by type — jockeyName, horseName, trainerName, or ownerName.Can I retrieve odds or live in-running race data?+
Does `get_race_results` return results for international tracks?+
country parameter is optional on get_race_results and get_track_entries, suggesting some international coverage, but the primary data reflects North American racing tracked by Equibase. Coverage depth for non-US tracks may vary. You can fork this API on Parse and revise it to narrow or expand the track scope as needed.Are workout data or past performances returned by any endpoint?+
get_horse_profile returns historical race records and career statistics including E-Speed figures, but structured workout entries are not part of the current response shape. You can fork this API on Parse and revise it to add a workout-focused endpoint.