Race-card monitoring
Use DraftKings Racing / DK Horse endpoints to turn race-card monitoring into repeatable API requests with documented inputs and JSON responses.
Follow the public race-card flow for DraftKings Racing, labeled DK Horse Racing on its current homepage: discover scheduled races, inspect the track directory, then resolve a race card by its ID. Race detail can include runners, post positions, published odds, and results; wagering controls and payout pools are not part of this API.
Browse DraftKings Racing (DK Horse)'s public track directory, scheduled race cards, and race-level horse data as JSON.
Endpoint families
1
Documented params
4
Examples
3
Live catalog snapshot
Active endpoints
3
Methods
GET
Required params
4
Schema refs
3
{
"platform": "DraftKings Racing / DK Horse",
"endpoint": "draftkings-racing-schedule",
"method": "GET",
"path": "/draftkings/racing/schedule",
"auth": "apiKey"
}Use cases
Browse DraftKings Racing (DK Horse)'s public track directory, scheduled race cards, and race-level horse data as JSON.
Use DraftKings Racing / DK Horse endpoints to turn race-card monitoring into repeatable API requests with documented inputs and JSON responses.
Use DraftKings Racing / DK Horse endpoints to turn track directory research into repeatable API requests with documented inputs and JSON responses.
Use DraftKings Racing / DK Horse endpoints to turn horse and post-position data collection into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live DraftKings Racing / DK Horse endpoint catalog — 3 endpoints, 4 documented request parameters, and 3 published response schemas — the same catalog Docs and Playground run against.
3 documented DraftKings Racing / DK Horse endpoints, all in the Racing family.
4 request parameters are documented across those DraftKings Racing / DK Horse endpoints, 4 of them required — the full input contract is public before you write any integration code.
3 of the 3 DraftKings Racing / DK Horse endpoints ship a recorded example response, and 3 carry a documented response schema — you can code against the real JSON before the first request.
DraftKings Racing / DK Horse endpoints document their error responses (400, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
3 hosted MCP tools back the DraftKings Racing / DK Horse endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/draftkings/racing/schedule
Endpoint catalog
/draftkings/racing/scheduleReturns public race-card metadata from the DraftKings Racing homepage, including track, race number, scheduled post time, and status. Favorite-track and wager data are excluded.
Response notes
scheduled races change throughout the day. It does not return runners, odds, results, or betting controls.
MCP tool draftkings_racing_schedule
/draftkings/racing/tracksReturns the public All Tracks directory with track type, status, schedule count, and country metadata. Favorite IDs, runner details, and wagering controls are excluded.
Response notes
`fetched_at` is when this API retrieved the page. Track type values currently shown by DraftKings are `Thoroughbred` and `Harness`; the endpoint returns all tracks and does not accept a type or location filter.
MCP tool draftkings_racing_tracks
/draftkings/racing/race/{race_id}Returns public race-card details for one race ID from DraftKings Racing, including entries, horse identifiers, morning-line and live odds, and finish positions when posted. It excludes pools, probable payouts, bet-form IDs, real-time WebSocket requests, favorites, and participant personal names.
MCP tool draftkings_racing_race_info
Related APIs
Sports & Gaming
Browse public sports and event data from FanDuel Sportsbook. Discover market-specific event types, follow a league or schedule, and read the markets and prices FanDuel publishes for that event and market.
Sports & Gaming
Follow public horse-racing cards across tracks and countries. Discover today's tracks, inspect races and runners, and read official results, wager-type reference data, and published pool information without placing a wager.
Sports & Gaming
Explore FanDuel Research's public editorial and sports-data surfaces. Discover sport slugs and teams, read articles and player updates, inspect live fixtures, and retrieve the published projection tables with their source-specific slate identifiers.
How to scrape DraftKings Racing / DK Horse
On 2026-10-25 the public DraftKings Racing homepage headed its product DK Horse Racing and showed a scheduled-races sidebar, an All Tracks directory, Featured Bets, and a Horse Betting 101 guide with sections on bet types, odds, and payouts. Crawlora exposes public race-card metadata and track data, not a bet slip or wagering account.
Call /draftkings/racing/schedule for the homepage's scheduled races, including track, race number, post time, status, and race_id. The schedule changes during the day and does not itself contain the runners or odds.
Use /draftkings/racing/tracks for the public All Tracks directory. For a schedule result, pass its race_id to /draftkings/racing/race/{race_id} to retrieve the individual race card.
The race-detail response can include horse names, post positions, live and morning-line odds, and finish positions when published. It excludes pools, payouts, bet IDs, and participant personal names.
FAQ
Use /draftkings/racing/schedule. Each listed race includes the race_id accepted by /draftkings/racing/race/{race_id}.
The /draftkings/racing/tracks endpoint lists track metadata and scheduled-race counts. Use /draftkings/racing/schedule for the current race cards and their post times.
No. These are read-only public data endpoints. They do not return pools or payouts and do not submit or manage wagers.