Meetings by date

GET /v1/meetings/{date}

One row per course on that day, with going and race count.

Available on

Free key 24h – 7d

Live today + 3 days

Archive back to 2017

Complete 2017 → upcoming

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
date	path	string	yes	YYYY-MM-DD.

Request

curl https://api.apihorseracing.com/v1/meetings/2021-02-28 \
  -H "X-API-Key: $AHR_KEY"

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

Response

200 OK application/json harvested 8 days ago

{
    "meta": {
        "request_id": "319dff7e4b3824a8",
        "data_as_of": "2026-09-12T05:10:27+00:00",
        "plan": "analyst",
        "window": "2017 → upcoming",
        "date": "2021-02-28",
        "count": 15
    },
    "data": [
        {
            "meeting_id": "mt_3W3QQ1S",
            "course_id": "cr_3GTJBD7",
            "course": "Aqueduct",
            "shortcode": null,
            "country": "USA",
            "region": "USA",
            "date": "2021-02-28",
            "going": "Sloppy",
            "surface": "Dirt",
            "weather": "Fine",
            "status": "DORMANT",
            "races": 8
        },
        {
            "meeting_id": "mt_2TRYEEK",
            "course_id": "cr_2YQ4YV7",
            "course": "Bordeaux Le Bouscat",
            "shortcode": null,
            "country": "FR",
            "region": "FR",
            "date": "2021-02-28",
            "going": "Very Soft",
            "surface": "Turf",
            "weather": "Cloudy",
            "status": "DORMANT",
            "races": 8
        },
        "… 13 more"
    ]
}

A real response from /v1/meetings/2021-02-28, 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
meeting_id	string	Opaque meeting identifier. A meeting is one course on one day.
course_id	string	Opaque course identifier.
course	string	Course name.
country	string	Country code as the source publishes it.
region	string	Jurisdiction, normalised. Welsh and Scottish racing is GB.
date	date	Race date, YYYY-MM-DD.
going	string	Ground description at the off.
surface	string	Turf, Dirt, Polytrack and so on.

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.
outside_window	403	You asked for a date your plan cannot see. The body names the window and the date you asked for. Search endpoints clamp instead of refusing, and report what they actually searched in meta.
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.

date

What this is for

One row per course racing on that date, with the going, the surface, the weather where it was published, and how many races the meeting held. No runners and no race detail.

It exists because a fixture list is a different question from a card. If you are showing "what is on today" you want nine rows, not four hundred runners, and fetching the full card to count meetings is wasteful on both sides.

Note that this path and /v1/meetings/{meeting_id} are the same shape. The router decides between them on the shape of what you send, so a date goes to this one and an identifier goes to the other. Send something that is neither and you get invalid_id rather than the wrong endpoint.

Common uses

A fixture list

Nine rows instead of four hundred. Cache it for the day.

Choosing a meeting to open

Take the meeting identifier from here and call /v1/meetings/{meeting_id} for its races.

Watching the going change

The going on a meeting is as published for the card. It can move during a day; re-fetch if that matters to you.