API reference

GreyhoundAPI documentation

Thirty-eight 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.

38REST endpoints

7On the free key

3Live Plus only

17Paginated

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" \
  -H "X-API-Key: $GAPI_KEY"

<?php
$ch = curl_init('https://api.greyhoundapi.com/v1/racecards/today?region=GB');
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', {
  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', {
      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",
    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 here3

01 Getting started Make your first GreyhoundAPI call in under five minutes: create a key, request today's racecards and read the response envelope. Read 02 Authentication How GreyhoundAPI keys work: the header format, live and sandbox prefixes, rotation with overlap, and what suspension looks like. Read 03 Sandbox tier The free GreyhoundAPI sandbox: list races and list tracks across every GB and AU track, over a rolling 1-7 day window. A scoped demo — every other endpoint needs a live key. Read

Reading a response5

04 Pagination Two ways to page GreyhoundAPI list endpoints: simple 1-based page numbers, or opaque cursors for large and streaming exports. Read 05 Errors The GreyhoundAPI error shape, every error code the API returns and the HTTP statuses to expect for each. Read 06 Timezones & dates How GreyhoundAPI handles time across Great Britain and Australia: UTC timestamps, track-local rendering and track-local date parameters. Read 07 Data freshness The GreyhoundAPI race lifecycle from scheduled to complete, honest delay metrics, and how to build consumers around results_received_at. Read 08 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

Limits & delivery4

09 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 10 WebSocket stream Stream greyhound results and race status changes over wss://: channels, the subscribe protocol, the replay window and connection limits. Read 11 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 12 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 The free sandbox now covers every track 2026-08-20 · 16 entries, newest first Read the changelog

/ 38 endpoints

Racecards 2 Races 6 Results 3 Meetings 3 Dogs 7 Trainers 5 Owners 3 Tracks 4 Breeding 2 Platform & reference 3

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.