Racecards and results

Meetings, cards and results by day, and how race times work.

The day's racing in three shapes: meetings (one row per course per day, with going and weather), racecards (every race and runner) and results (settled races, with finishing order and starting prices).

• GET /v1/meetings/calendar: Thirty days back and the week ahead, one row per UK course per day.
• GET /v1/meetings/{date}: Every UK meeting on a date, with going and weather.
• GET /v1/meetings/{meeting_id}: One meeting and every race on it.
• GET /v1/racecards/today: Today's UK cards, grouped by meeting.
• GET /v1/racecards/upcoming: Declarations for the next few days.
• GET /v1/racecards/{date}: The full UK card for any date.
• GET /v1/results/latest: The latest settled UK races your plan can read.
• GET /v1/results/yesterday: Every settled UK race from yesterday.
• GET /v1/results/{date}: Settled UK races for a date.

Days and times

A date is the course's own racing day, YYYY-MM-DD. A race time is the racecourse clock. Every other time is UTC.

How it links

Each meeting has a meeting_id and each race a race_id: pass a race id to the race endpoints for its market, result and dividends.

Common jobs

• Today's cards on your site: GET /v1/racecards/today, refreshed every couple of minutes on race days.
• Yesterday's results every morning: GET /v1/results/yesterday, on every plan.
• A month's fixtures: GET /v1/meetings/calendar.
• Any day since 2017: GET /v1/racecards/{date} or GET /v1/results/{date} on Archive and Complete.