Discover/Thegreyhoundrecorder API
live

Thegreyhoundrecorder APIthegreyhoundrecorder.com.au ↗

Access Australian & NZ greyhound race cards, meeting schedules, and per-runner form stats from thegreyhoundrecorder.com.au via 3 structured endpoints.

Endpoint health
monitored
get_race_card
list_meetings
get_race_form
0/3 passing latest checkself-healing
Endpoints
3
Verified account required
Updated
1h ago

What is the Thegreyhoundrecorder API?

The Greyhound Recorder API exposes 3 endpoints that cover Australian and New Zealand greyhound racing: upcoming meeting schedules, full race cards with every runner's breeding and trainer details, and per-race form guides including career and track statistics. The get_race_form endpoint returns runner-level stats blocks — career, track, and track/distance records as runs:wins-seconds-thirds strings — alongside best-time figures and recent form strings.

This call costs1 credit / call— charged only on success
Try it
Meeting date filter, ISO YYYY-MM-DD (local track date). Omitted = all dates on the index.
→ api.parse.bot/scraper/bd4da411-b6a7-4379-9707-bc7fe2035876/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/bd4da411-b6a7-4379-9707-bc7fe2035876/list_meetings?date=2026-10-05' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 3 totalmissing one? ·

Lists the upcoming Australian & NZ greyhound meetings currently shown on the site's form-guide index (normally today plus the next several days), each with its race list (race_id, race_number, race_slug, name, status). One round trip. meeting_slug is the key for get_race_card; race_slug (with meeting_slug) is the key for get_race_form. Optional date filter narrows to one meeting date; a date outside available_dates returns an empty meetings list (count 0). Meetings not yet at final-fields stage (meeting_stage Nominations/Acceptances) may list races with a null race_number.

Input
ParamTypeDescription
datestringMeeting date filter, ISO YYYY-MM-DD (local track date). Omitted = all dates on the index.
Response
{
  "type": "object",
  "fields": {
    "count": "number of meetings returned after filtering",
    "meetings": "array of meeting objects: meeting_id, meeting_slug, meeting_date, track, state, track_abbrev, country, meeting_stage, race_count, races[] (race_id, race_number, race_slug, name, status)",
    "date_filter": "the date filter applied, or null",
    "available_dates": "array of ISO dates that have meetings on the index"
  },
  "sample": {
    "data": {
      "count": 7,
      "meetings": [
        {
          "races": [
            {
              "name": "Sky Racing Maiden Stake Ctb Division1",
              "status": "open",
              "race_id": "3442902",
              "race_slug": "sky-racing-maiden-stake-ctb-division1-race-1",
              "race_number": 1
            }
          ],
          "state": "SA",
          "track": "Angle Park",
          "country": "AUS",
          "meeting_id": "452329",
          "race_count": 12,
          "meeting_date": "2026-10-05",
          "meeting_slug": "angle-park-20261005",
          "track_abbrev": "APK",
          "meeting_stage": "FinalFields"
        }
      ],
      "date_filter": "2026-10-05",
      "available_dates": [
        "2026-10-02",
        "2026-10-03",
        "2026-10-04",
        "2026-10-05",
        "2026-10-06"
      ]
    },
    "status": "success"
  }
}

About the Thegreyhoundrecorder API

Meeting Discovery

list_meetings returns every greyhound meeting currently listed on the form-guide index, which typically spans today and the next several days. Each meeting object includes meeting_slug, meeting_date, track, state, country, track_abbrev, and a nested array of races each carrying race_id, race_number, race_slug, and status. The optional date parameter (ISO YYYY-MM-DD) filters results to a single local track date. The response also surfaces available_dates so you can enumerate what's on the index before committing to a specific meeting.

Race Cards

get_race_card takes a meeting_slug of the form <track-slug>-<yyyymmdd> and returns the full field for every race at that meeting. Each race object carries distance_m, grade, start_time_utc, prize_money, a preview comment, and is_resulted / is_abandoned flags. Runner objects include box, dog_id, dog_name, dog_slug, colour, sex, age, whelped date, sire, dam, owner, trainer, and official race ratings where available. The meeting_stage field (e.g. FinalFields) indicates how settled the field is.

Per-Race Form Guide

get_race_form accepts both a race_slug and a meeting_slug and returns a detailed form guide for that race. Each runner in the runners array is extended with a stats block containing career, track, and track_distance records formatted as runs:wins-seconds-thirds strings, a best_track_distance_sec numeric best time, and a recent form string showing finishing positions over the last several starts. The is_resulted boolean lets you check whether results are already posted before processing runners.

Reliability & maintenance

The Thegreyhoundrecorder API is a managed, monitored endpoint for thegreyhoundrecorder.com.au — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when thegreyhoundrecorder.com.au changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official thegreyhoundrecorder.com.au API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Latest check
0/3 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build a greyhound form guide app showing box draws, trainer, and career stats for upcoming Australian races
  • Aggregate start_time_utc fields across meetings to drive a live race schedule or countdown widget
  • Compare track_distance win rates across runners in a race to inform pre-race modelling
  • Track best_track_distance_sec times to identify track specialists at a given venue
  • Monitor is_resulted flags across a day's races to detect when results become available
  • Filter list_meetings by country or state to scope a regional greyhound data feed
  • Combine sire and dam fields from get_race_card to build a greyhound breeding database
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does thegreyhoundrecorder.com.au offer an official developer API?+
The Greyhound Recorder does not publish a public developer API or documented data feed. This Parse API provides structured programmatic access to the data on their form-guide pages.
What does `list_meetings` return and how does the date filter work?+
It returns all meetings on the form-guide index, typically today through the next several days. Each meeting includes its meeting_slug, track, state, country, and a nested list of races. Passing a date parameter in YYYY-MM-DD format restricts results to meetings whose local track date matches. The available_dates array in every response tells you which dates are currently on the index.
Does the API return race results or finishing times?+
The is_resulted boolean flag on each race indicates whether a result has been posted, and the form string on each runner in get_race_form reflects recent finishing positions. Full result margins, sectional times, and finishing order for completed races are not currently returned as structured fields. You can fork this API on Parse and revise it to add a results endpoint.
Does the API cover TAB or bookmaker odds?+
Odds are not currently included in any endpoint response. The API covers identity, breeding, trainer, grade, distance, and form statistics. You can fork this API on Parse and revise it to add an odds or market data endpoint if that data becomes accessible.
How fresh is the race card data, and are late scratchings reflected?+
Race card data reflects what is currently published on the Greyhound Recorder form-guide pages. The meeting_stage field (e.g. FinalFields) indicates the field's settlement state, which can help distinguish provisional fields from final draws. Because data freshness depends on when the source site updates, polling get_race_card close to race time will give the most current view of scratchings.
Page content last updated . Spec covers 3 endpoints from thegreyhoundrecorder.com.au.
Related APIs in SportsSee all →
racenet.com.au API
Access data from racenet.com.au.
form.tab.com.au API
Access data from form.tab.com.au.
gbgb.org.uk API
Access comprehensive greyhound racing information including race results, meeting details, greyhound profiles and form history, and upcoming open races across all GBGB tracks. Search for specific races and greyhounds, browse available tracks and race classes, and stay updated on upcoming racing events.
racingtv.com API
Access detailed information about UK and international horse racing meetings, including complete racecards, runner details, Timeform analysis, pace bias data, and draw commentary. Plan your racing strategy or stay informed on upcoming races with comprehensive meeting schedules and expert insights all in one place.
racingpost.com API
Access comprehensive horse racing data from Racing Post, including daily racecards, meeting schedules, race results, and detailed horse profiles with form history, stats, and pedigree.
sportinglife API
Access comprehensive UK and Irish horse racing racecards from Sporting Life to view meeting schedules, race details, and detailed runner information with form analysis. Plan your betting strategy with up-to-date racecard data including horse forms and race conditions all in one place.
tab.com.au API
Access live horse racing meetings, race cards, fixed odds, and results from TAB Australia. Retrieve real-time sports betting information and racing data, including upcoming races, current odds, and historical race outcomes.
race.netkeiba.com API
Access comprehensive Japanese horse racing data from netkeiba.com, including race schedules, detailed race cards with runner information (jockeys, weights, equipment), and complete race results with finishing orders, times, lap splits, and payouts. Use this data to research races by date, analyze runner details before competitions, and review detailed race outcomes and performance metrics.