tab.com.au APItab.com.au ↗
Retrieve horse racing meetings, race cards, fixed odds, and results from TAB Australia. Covers thoroughbred, harness, and greyhound racing across all states.
curl -X GET 'https://api.parse.bot/scraper/5137d70d-0c2b-4de4-a5a9-1554bd34c3e9/get_racing_meetings_by_date' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve all racing meetings for a given date across all race types.
| Param | Type | Description |
|---|---|---|
| date | string | Date in YYYY-MM-DD format. Defaults to today. |
| jurisdiction | string | State jurisdiction code (NSW, VIC, QLD, etc.) |
{
"type": "object",
"fields": {
"meetings": "array"
},
"sample": {
"meetings": [
{
"raceType": "R",
"venueCode": "R",
"meetingName": "RANDWICK"
}
]
}
}About the tab.com.au API
The TAB.com.au API exposes 5 endpoints covering Australian racing meetings, race cards, fixed odds, and results. Use get_racing_meetings_by_date to pull all meetings for a given day filtered by jurisdiction, or hit get_next_to_jump_races for a live feed of upcoming races across all venues and race types without specifying any parameters.
Racing Meetings and Next to Jump
get_racing_meetings_by_date returns a meetings array for any date in YYYY-MM-DD format, optionally filtered by a state jurisdiction code (NSW, VIC, QLD, etc.). Omit the date parameter and it defaults to today. get_next_to_jump_races takes no inputs and returns a races array reflecting the current queue of imminent races across all venues — useful for real-time dashboards or alert systems that need to react to race start times without polling a full meeting list.
Race Cards and Fixed Odds
Both get_race_card and get_race_fixed_odds require four identifying parameters — date, venue (as a name slug), venue_code, and race_number — plus a race_type of thoroughbred, harness, or greyhound. get_race_card returns a runners array and a raceName string, giving you the full field for a specific race. get_race_fixed_odds returns a fixedOdds array reflecting current TAB-listed odds for each runner in that race.
Race Results
get_race_results uses the same five-parameter signature and returns a results array alongside a dividends object once a race is complete. The dividends object covers payout data for the applicable bet types for that race. This endpoint is only meaningful after a race has been run — querying a future race will not return result data.
Coverage Notes
The API covers the three race types TAB supports: thoroughbred, harness, and greyhound racing. All endpoints that target a specific race share a consistent parameter set, so venue and date references are interchangeable across the race card, odds, and results calls for the same event.
- Build a race-day dashboard that lists all Australian meetings by state using
get_racing_meetings_by_datefiltered by jurisdiction code - Power a 'next to jump' widget on a betting or sports news site using the
get_next_to_jump_racesendpoint - Display full race fields including runner names by fetching the
runnersarray fromget_race_card - Track current fixed odds movements for a specific race by polling
get_race_fixed_oddson a schedule - Record historical race outcomes and dividends by querying
get_race_resultsafter each race completes - Build a multi-race comparison tool for greyhound or harness races by iterating race numbers across a venue
- Alert users when a monitored runner's odds change by comparing successive
fixedOddsarray responses
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does TAB.com.au have an official developer API?+
What does get_race_fixed_odds return, and how current is the data?+
fixedOdds array for the specified race, reflecting TAB's current fixed-price odds for each runner. Odds on TAB can change up to race start, so the freshness of the data depends on when you call the endpoint. For live odds tracking, periodic polling is the appropriate approach.Does the API cover sports betting markets, not just racing?+
Can I retrieve results and dividends for exotic bets like trifectas or first fours?+
get_race_results returns a dividends object that reflects payout data for the applicable bet types for that race. The specific bet types included in the dividends object depend on what TAB settles for each race. If you need to filter or expand dividend coverage beyond what the current endpoint returns, you can fork the API on Parse and revise the endpoint logic.Do I need both venue and venue_code to query a specific race?+
get_race_card, get_race_fixed_odds, and get_race_results all require both the venue slug and the venue_code alongside the date, race_type, and race_number. You can obtain the venue slug and code from the meetings array returned by get_racing_meetings_by_date.