USA and Canada Horse Racing Data Is Live: API and Daily Files

North American racing is now on HorseRaceDatabase. The USA + Canada Dataset API covers 90+ tracks across the United States and Canada, and the USA + Canada Daily Update Service delivers the same data as files every morning.

No tips. No predictions. Just the data, on the right date.

What is in it

• Tracks: 90+ across the United States and Canada, including Churchill Downs, Saratoga, Santa Anita, Gulfstream Park, Keeneland, Del Mar and Woodbine.
• Results from 1 January 2025: about 68,000 races, about 509,000 runner results and about 72,700 horses, updated every morning for the previous race day.
• Per runner: finishing position, draw, weight, jockey, trainer, starting price and favourite.
• Racecards: the declared runners for today and tomorrow, with draw, weight, age, jockey and trainer, plus the odds once they are published (usually on race day). Refreshed twice a day.
• Profiles: horses, jockeys and trainers with career figures (runs, wins, placed, rates), split by race type: Flat Dirt, Flat Turf and Flat AW. About three in four North American races since 2025 are on dirt, so the dirt split is the one that usually matters.

For scale: the UK averages about 36 races on a racing day. North America runs about 100 on a typical day, across all its tracks.

The clock problem we solved first

North American racing runs across several time zones, and an evening card on the West Coast finishes after midnight in the UK. Store that race on the UK date and it lands on the wrong day.

It is not a rare edge case. Since 2025, 19,635 North American races, more than one in four and about 29 a day, ran on a local race date different from the UK date.

So every race carries both clocks:

• date and race_time: the race date and post time at the track;
• timezone: the track’s time zone, for example America/Los_Angeles or America/Toronto;
• post_time_utc: the same moment in UTC;
• date_uk and time_uk: the same moment on the UK clock.

A real example from the API reference: Del Mar, race 8, race date 2026-11-06, post time 16:03 in America/Los_Angeles. That is 00:03 on 7 November in the UK, and 2026-11-07T00:03:00 in UTC. The race stays on its own race day, and you can still line it up with UK data when you need to.

Two ways to use it

The USA + Canada Dataset API

The same JSON format as our UK and Hong Kong APIs, so one parser serves every region. Endpoints start with /usa/: races, results, racecards, horses, jockeys and trainers.

Keeping up is cheap. /usa/records/ returns the last race day with results, and /usa/records/date/{date} reads any of the last seven race days in pages of 50 runners. A typical North American day is about 16 pages, which leaves most of the plan for history.

Essential is EUR 34.90 a month (12,000 calls) or EUR 349 a year (144,000 calls, available from day one), with the current and previous calendar year of history. The monthly plan starts with a 7-day free trial: 100 calls with the full Essential window. A card is required, and nothing is charged if you cancel before the trial ends.

The USA + Canada Daily Update Service

If you prefer files to an API: every morning, two files in your account are refreshed, with the last seven race days of results and the day’s racecards, in CSV, SQL and JSON. EUR 34.90 a month, plus a one-off EUR 34.90 sign-up fee.

What it does not do

Better to know this before you build on it:

• Racecards start from November 2026. There are no older cards and no past performances.
• Beaten distances are not published for North American races.
• Sectional times are available at the 19 tracks that publish them, from late December 2025, about 48 hours after each race.
• History starts in 2025.
• It is a daily update, not a live feed.

Where to start

Pick USA + Canada on the API page and start the trial, or choose the Daily Update Service for files. Already on our UK or Hong Kong API? The code you wrote moves across: one API key per region, one format for all three.