Casualties

GET /v1/courses/{course_id}/casualties

Non-completion rates by run type.

Available on

Free key not on this plan

Live not on this plan

Archive not on this plan

Complete not on this plan

Complete + Analyst 2017 → upcoming

Send your key in the X-API-Key header, or as ?key= if your tool cannot set one. A date outside your plan's window returns 403 outside_window naming the window, never an empty array.

Parameters

Name	In	Type	Required	Description
course_id	path	string	yes	Opaque course identifier.
run_type	query	string	no	Restrict to Hurdle, Chase or NH Flat. Casualties in flat racing are rare enough to be uninformative.
going	query	string	no	Restrict to one going.

Request

curl https://api.apihorseracing.com/v1/courses/cr_JSRC8Z/casualties \
  -H "X-API-Key: $AHR_KEY"

$ch = curl_init('https://api.apihorseracing.com/v1/courses/cr_JSRC8Z/casualties');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => ['X-API-Key: ' . getenv('AHR_KEY')],
]);
$data = json_decode(curl_exec($ch), true)['data'];

const res = await fetch(
  'https://api.apihorseracing.com/v1/courses/cr_JSRC8Z/casualties',
  { headers: { 'X-API-Key': process.env.AHR_KEY } }
);
const { meta, data } = await res.json();

import os, requests

r = requests.get(
    "https://api.apihorseracing.com/v1/courses/cr_JSRC8Z/casualties",
    headers={"X-API-Key": os.environ["AHR_KEY"]},
).json()

Response

200 OK application/json harvested 8 days ago

{
    "meta": {
        "request_id": "e6d53562f62534b0",
        "data_as_of": "2026-09-12T05:10:27+00:00",
        "plan": "analyst",
        "window": "2017 → upcoming",
        "count": 20
    },
    "data": {
        "course_id": "cr_JSRC8Z",
        "course": "Fontwell",
        "window": {
            "from": null,
            "to": null,
            "note": "The whole archive. Your plan sets no date limit."
        },
        "casualties": [
            {
                "run_type": null,
                "casualty": "PulledUp",
                "runners": 821,
                "of_runs": 7266,
                "rate": 0.113
            },
            {
                "run_type": null,
                "casualty": "Fell",
                "runners": 112,
                "of_runs": 7266,
                "rate": 0.0154
            },
            "… 18 more"
        ]
    }
}

A real response from /v1/courses/cr_JSRC8Z/casualties, captured by calling the live API rather than written by hand.

Response fields

Each field is described once and rendered on every endpoint that returns it, so the wording cannot drift between pages.

Field	Type	What it is
course_id	string	Opaque course identifier.
course	string	Course name.
window	string	How far back and forward that plan can read.
run_type	string	Flat, Hurdle, Chase or NH Flat.
casualty	string	Why a runner did not complete: PulledUp, Fell, UnseatedRider, BroughtDown, RefusedToRace, RanOut.
runners	integer	Runners who took part.

What varies by jurisdiction

Run type is filled in behind the results crawl

The code a race was run under lives on the horse profile rather than the race, so it arrives on a later pass. A null run_type means not yet fetched, not unclassified.

Errors this endpoint returns

Code	Status	When
unauthorized	401	No key, or one we do not recognise. Check the header name and that the key has not been rotated from your account page.
upgrade_required	403	The endpoint returns computed statistics and your plan does not include them. The body names every plan that does reach it, so you never have to look it up.
not_found	404	The identifier is well formed but nothing has it. Distinct from invalid_id, which means the identifier itself is wrong.
invalid_id	422	The prefix does not match the kind of thing the path expects, or the identifier is malformed. A horse id passed where a race is wanted lands here rather than returning the wrong race.
invalid_param	422	A date that is not YYYY-MM-DD, a by= dimension we do not have, or a cursor that did not come from us. The message names the parameter.
rate_limited	429	Past your per-minute rate. Retry-After is set, and X-RateLimit-Remaining tells you where you stand on every successful response too.
server_error	500	Ours, not yours. Every response carries a request_id; quote it and we can find the exact request.

Run it live

A real request from your browser straight to api.apihorseracing.com with your own key. Nothing is proxied and nothing is logged by this page.

Your API key

Remembered in this browser so you do not paste it on every page.

course_id

run_type optional

going optional

What this is for

Non-completion rates here, by run type and reason: pulled up, fell, unseated, brought down, refused to race and ran out.

This is a jumps endpoint in practice. Britain records a casualty on about five percent of all runners, and almost all of that is in hurdles and chases, where completing at all is a meaningful part of the outcome.

It only works where the jurisdiction publishes a reason. Britain, Ireland, France, South Africa and Germany do; America largely does not, so an American course will return very little here. That is a limit of the source rather than of the query, and the coverage page has the measured figures.

A word on what this is not. These are non-completions, not injuries or fatalities. We do not hold that data and would not publish an inference about it from this.

Common uses

Assessing a stiff track

Some chase courses are markedly harder to get round. The rate per run type shows it plainly.

Understanding a ground effect

Casualty rates move with the going, and by different amounts at different tracks.

Modelling completion

In a jumps race the probability of getting round is a real part of the price, and this is the base rate for it.