APIHorseRacing

API reference

Documentation

63 REST endpoints over horse racing in eleven jurisdictions: racecards, results, starting prices, price movement, book percentages, horses, trainers, jockeys, owners and courses. Race data only. No predictions, no ratings, no betting advice.

63REST endpoints
37On the free key
24Analyst only
9Paginated

Machine readable: OpenAPI 3.1 · Postman collection · Changelog. Both are generated from the same registry as these pages, so a client you generate cannot describe an endpoint that does not exist. Every endpoint page has a Run it live console; bring your key.

Quickstart

Base URL https://api.apihorseracing.com, your key in the X-API-Key header, JSON back in a meta and data envelope. This is the whole of it:

curl https://api.apihorseracing.com/v1/racecards/today \
  -H "X-API-Key: $AHR_KEY"

New here? Read Getting started, then Coverage by country and Errors. Those three are the difference between a call that works and an integration that behaves.

Guides

22

Read these before the reference. They answer the questions the reference assumes you already know.

CHANGELOG Price movement on every runner 9 September 2026 · 8 entries, newest first Read the changelog

Reference & coverage

7

What exists, and how much of it. Call these before writing anything else.

Race reports

2

A written account of every race, from the records themselves.

Racecards & meetings

7

Today, tomorrow, and any day in the archive.

Races & markets

7

One race, in as much detail as exists.

Horses & pedigree

8

Form, breeding, and whether a horse is improving.

Trainers

7

A yard, and how it has actually paid.

Jockeys & owners

10

The same shapes as trainers, deliberately.

Webhooks & account

3

Being told, instead of asking.

Courses & bias

6

What a track does to a race.

Market & analysis

6

The market itself, across the whole archive.

Nothing matches that. Try a shorter word, or clear the plan filters.