Ask your own question

Parameters

Request

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

$ch = curl_init('https://api.apihorseracing.com/v1/analysis/angles');
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/analysis/angles',
  { 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/analysis/angles",
    headers={"X-API-Key": os.environ["AHR_KEY"]},
).json()

curl https://api.apihorseracing.com/v1/analysis/angles?key=$AHR_KEY

$url  = 'https://api.apihorseracing.com/v1/analysis/angles' . '?key=$AHR_KEY';
$data = json_decode(file_get_contents($url), true)['data'];

const res = await fetch(
  'https://api.apihorseracing.com/v1/analysis/angles?key=$AHR_KEY'
);
const { meta, data } = await res.json();

import os, requests

r = requests.get(
    "https://api.apihorseracing.com/v1/analysis/angles?key=$AHR_KEY",
).json()

Response

{
    "meta": {
        "request_id": "66fb147338518557",
        "data_as_of": "2026-09-12T05:10:27+00:00",
        "plan": "analyst",
        "window": "2017 → upcoming"
    },
    "data": {
        "window": {
            "from": null,
            "to": null,
            "note": "The whole archive. Your plan sets no date limit."
        },
        "filters": {
            "run_type": "Chase",
            "favourite": "1",
            "min_runners": "12"
        },
        "overall": {
            "runs": 1263,
            "priced": 1263,
            "first": 280,
            "second": 190,
            "third": 147,
            "fourth": 113,
            "win_pct": 0.2217,
            "top3_pct": 0.4885,
            "expected_wins": 257.67,
            "a_e": 1.087,
            "a_e_range": [
                0.959,
                1.214
            ],
            "a_e_beats_market": false,
            "significant": false,
            "low_sample": false,
            "pl_1pt": -252.49,
            "roi_pct": -19.99
        }
    }
}

A real response from /v1/analysis/angles?run_type=Chase&favourite=1&min_runners=12, 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.

What varies by jurisdiction

Errors this endpoint returns

Run it live

What this is for

Ask your own question. Every filter in the statistics engine, combined freely, returning the standard block grouped however you like. Chase handicaps on soft ground at fourteen runners or more, grouped by draw. Whatever you can describe.

This is the endpoint the Analyst tier is really for. The rest are convenient shapes for common questions; this one is the engine underneath them with the filters exposed.

It is also the easiest way in the whole API to fool yourself, and that is worth saying plainly rather than burying. Combining seven filters until something looks significant is not analysis, it is searching for noise, and with a million and a half runner records you will always find some. Every response therefore carries the runner count and the interval, and rows under about a hundred runners are flagged low_sample.

The honest way to use it is to decide the question before you run it, and to treat anything you find by exploring as a hypothesis to test on a period you did not look at.

Common uses

Notes

The filters are combined with AND. There is no OR, deliberately: it makes queries whose sample size is impossible to reason about.

Related in Market & analysis