API reference

GreyhoundAPI documentation

Sixty-two REST endpoints and a WebSocket stream over greyhound racing in Great Britain and Australia: racecards, runners, results, sectionals, starting prices, Betfair market summaries, dogs, trainers, owners, tracks and breeding. Race data only — no predictions, no ratings, no betting advice.

62REST endpoints

17On the free key

20Live Plus only

22Paginated

Machine-readable: OpenAPI 3.1 spec · Postman collection · generated from the same registry as these pages · Changelog. Every endpoint page has a Run it live console — bring a key.

Quickstart

Base URL https://api.greyhoundapi.com/v1, key in the X-API-Key header, JSON in a meta/data envelope. First call:

curl "https://api.greyhoundapi.com/v1/racecards/today?region=GB&summary=true" \
  -H "X-API-Key: $GAPI_KEY"

<?php
$ch = curl_init('https://api.greyhoundapi.com/v1/racecards/today?region=GB&summary=true');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => ['X-API-Key: ' . getenv('GAPI_KEY')],
]);
$response = json_decode(curl_exec($ch), true);
curl_close($ch);

print_r($response['data']);

const res = await fetch('https://api.greyhoundapi.com/v1/racecards/today?region=GB&summary=true', {
  headers: { 'X-API-Key': process.env.GAPI_KEY }
});
if (!res.ok) throw new Error(`GreyhoundAPI ${res.status}`);
const { meta, data } = await res.json();
console.log(meta.data_as_of, data);

import { useEffect, useState } from 'react';

export default function Example() {
  const [data, setData] = useState(null);

  useEffect(() => {
    fetch('https://api.greyhoundapi.com/v1/racecards/today?region=GB&summary=true', {
      headers: { 'X-API-Key': import.meta.env.VITE_GAPI_KEY }
    })
      .then((r) => r.json())
      .then((body) => setData(body.data));
  }, []);

  if (!data) return <p>Loading…</p>;
  return <pre>{JSON.stringify(data, null, 2)}</pre>;
}

Browser code exposes whatever key it ships with — use a sandbox key for prototypes and proxy live keys through your own server in production.

import os
import requests

r = requests.get(
    "https://api.greyhoundapi.com/v1/racecards/today?region=GB&summary=true",
    headers={"X-API-Key": os.environ["GAPI_KEY"]},
    timeout=10,
)
r.raise_for_status()
body = r.json()
print(body["meta"]["data_as_of"], body["data"])

New here? Read Getting started, then Timezones & dates and Data freshness — the two guides that make a GB + AU racing consumer behave correctly.

Guides

Read these before the reference — they are the difference between a call that works and an integration that behaves.

Start here8

01 Start with a free key Everything a free GreyhoundAPI key can do, the seven endpoints it reaches, and a first request that works straight away. Read 02 Race Day plan overview Today and yesterday, with the prices on: what the Race Day plan covers, every endpoint it reaches, and what still needs Live. Read 03 Getting started Make your first GreyhoundAPI call in under five minutes: create a key, request today's racecards and read the response envelope. Read 04 Authentication How GreyhoundAPI keys work: the header format, live and sandbox prefixes, rotation with overlap, and what suspension looks like. Read 05 Sandbox tier The free GreyhoundAPI key: today's cards and results, the days ahead and the last few days, across every GB, AU and IE track. Prices, weights and weather are on the paid plans. Read 06 MCP server for Claude and ChatGPT Connect GreyhoundAPI to Claude, ChatGPT or any Model Context Protocol client and ask about GB and Australian greyhound racing in plain English. How to set it up, which tools the assistant gets, and how it decides which to call. Read 07 What we cover Which tracks are in the archive, how often each races, and where the edges are. Read 08 The whole API in one file Every endpoint, parameter, sample and guide as a single markdown document, for offline reading or for pasting into an assistant. Read

Coverage & integrity4

09 Data integrity Check what we hold for any date before you pay for it — races carded, results recorded, and anything without a result, with the reason. Read 10 Data freshness The GreyhoundAPI race lifecycle from scheduled to complete, honest delay metrics, and how to build consumers around results_received_at. Read 11 Historical data What history GreyhoundAPI holds, which detail lives inside results versus dedicated endpoints, and how to bulk-import the archive for analysis or model training. Read 12 Weather at the track Where the weather on a race comes from, which hour it belongs to, what before_race measures, and which races carry none. Read

Reading a response5

13 Batch requests Fetch up to 50 known records in one call with the ids parameter, instead of one request per record. Read 14 Pagination Two ways to page GreyhoundAPI list endpoints: simple 1-based page numbers, or opaque cursors for large and streaming exports. Read 15 Errors The GreyhoundAPI error shape, every error code the API returns and the HTTP statuses to expect for each. Read 16 Timezones & dates How GreyhoundAPI handles time across Great Britain and Australia: UTC timestamps, track-local rendering and track-local date parameters. Read 17 Live odds Best Betfair back and lay prices, when they arrive, how often they update, and what the numbers do and do not mean. Read

Limits & delivery4

18 Rate limits Per-minute and monthly limits for live and sandbox GreyhoundAPI keys, the rate-limit response headers and how to back off cleanly. Read 19 WebSocket stream Stream greyhound results and race status changes over wss://: channels, the subscribe protocol, the replay window and connection limits. Read 20 Webhooks Push race status changes and result publication to your own HTTPS endpoint: events, the signed payload, retries and how to verify a delivery. Read 21 Browser extension A Chrome extension that watches API status and server ping from your toolbar, with desktop alerts when the results pipeline falls behind. Read

Changelog Australian prize money and tote dividends 2026-10-08 · 48 entries, newest first Read the changelog

/ 62 endpoints

Racecards 2 Races 12 Results 4 Weather 1 Race commentary 5 Meetings 5 Dogs 10 Trainers 5 Owners 3 Tracks 4 Breeding 6 Platform & reference 5

Racecards

Upcoming greyhound racecards for Great Britain and Australia — every scheduled race with runners, traps, grades, distances and track-local start times, resolved per calendar day.

GET /v1/racecards/today

Today's racecards

Every greyhound racecard scheduled today in Great Britain and Australia, resolved per track-local calendar day, with runners, traps, grades and start times.

Free key Paged

GET /v1/racecards/upcoming

Upcoming races

A rolling window of the next greyhound races to jump across GB, AU and IE, from the next hour up to the next 48, ordered by scheduled start time.

Free key Paged

Races

Search and retrieve individual greyhound races: full runner line-ups, grades, going, off-times, lifecycle status, results and starting-price and Betfair market summaries for any race in the archive.

GET /v1/races

Search races

Search the full greyhound race archive by date range, region, track, grade, distance, handicap flag and lifecycle status, with cursor pagination.

Free key Paged

GET /v1/races/{race_id}

Get a race

Full detail for one greyhound race: track, grade, distance, going, scheduled and official off-times, lifecycle status, freshness metadata and the complete runner line-up.

Free key

GET /v1/races/{race_id}/runners

Race runners

Just the runners for one race: trap draws, dogs, breeding, trainers, owners, weights — and positions, times and prices once the result is in.

Free key

GET /v1/races/{race_id}/result

Get a race result

The result view of a race: finishing order, starting prices, sectionals, run times, beaten distances, dividends and the exact off and receipt times.

GET /v1/races/{race_id}/status

Race status & freshness

The lifecycle and freshness record of a race: current status, official off delay, when results arrived and how far behind the scheduled start they were.

GET /v1/races/{race_id}/precedents

Race precedents

Races from the archive that ran under matching conditions at this track and distance, with what actually happened in them — and an explicit list of what each one matched on and where it differs.