Discover/Racing TV API
live

Racing TV APIracingtv.com

Access UK and international horse racing meetings, racecards, runners, Timeform ratings, pace bias, and draw commentary via the Racing TV API.

This API takes change requests — .
Endpoint health
verified 4h ago
get_racecard
list_meetings
1/2 passing latest checkself-healing
Endpoints
2
Updated
4h ago

What is the Racing TV API?

The Racing TV API covers 2 endpoints that expose horse racing meeting schedules and full racecards, including Timeform analysis, pace bias, and draw commentary. list_meetings returns all meetings on a given date with per-race summaries, while get_racecard delivers complete runner-level data — jockey, trainer, weight, draw, form, and Timeform verdict — for any specific race identified by date, track, and start time.

Try it
Meeting date in ISO format YYYY-MM-DD.
ISO country code to filter meetings (e.g. 'gb' for Great Britain, 'ie' for Ireland). Omitted returns all countries.
api.parse.bot/scraper/10d6703d-2d60-4488-81df-a788954363bc/<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/10d6703d-2d60-4488-81df-a788954363bc/list_meetings?date=2026-07-16&country=gb' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace racingtv-com-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: Racing TV SDK — bounded, re-runnable; every call capped."""
from parse_apis.racingtv_com_api import RacingTv, RaceNotFound

client = RacingTv()

# List today's UK meetings with their races
for meeting in client.meetings.list(date="2026-07-15", country="gb", limit=3):
    print(meeting.track_name, meeting.track_condition, f"({len(meeting.races)} races)")

# Get a specific racecard with full Timeform data and pace analysis
racecard = client.racecards.get(date="2026-07-15", track="catterick-bridge", time="1410", limit=1).first()

# Inspect runners with Timeform comments and ratings
if racecard:
    for runner in racecard.runners[:3]:
        print(runner.horse_name, runner.timeform_rating, runner.weight, runner.jockey_name)

# Typed error: wrap a call that may not find a race
try:
    missing = client.racecards.get(date="2026-07-15", track="nonexistent", time="0000", limit=1).first()
except RaceNotFound as e:
    print(f"race not found: {e.track} at {e.time}")

print("exercised: meetings.list, racecards.get")
All endpoints · 2 totalmissing one? ·

Lists race meetings for a given date with their scheduled races. Each meeting includes track details, going conditions, and a summary of each race (time, distance, class, prize). Filter by country ISO code to narrow to UK-only or Irish meetings. Results are a single page of all meetings for the date.

Input
ParamTypeDescription
daterequiredstringMeeting date in ISO format YYYY-MM-DD.
countrystringISO country code to filter meetings (e.g. 'gb' for Great Britain, 'ie' for Ireland). Omitted returns all countries.
Response
{
  "type": "object",
  "fields": {
    "meetings": "array of meeting objects, each with track info and nested races",
    "meeting_date": "string — the requested date"
  },
  "sample": {
    "meetings": [
      {
        "date": "2026-07-15",
        "races": [
          {
            "id": 704313,
            "prize": "Winner: £3,974.00",
            "title": "Aja Novice Flat Amateur Jockeys' Handicap",
            "distance": "1m 4f 13y",
            "race_type": "Flat",
            "race_class": "5",
            "start_time": "2026-07-15T14:10:00+01:00",
            "track_type": "Turf",
            "eligibility": "4YO+",
            "rating_range": "0-70",
            "runner_count": "6 runners"
          }
        ],
        "country": "gb",
        "weather": "sunny",
        "meeting_id": 177543,
        "track_name": "Catterick Bridge",
        "track_slug": "catterick-bridge",
        "tv_channel": "RTV",
        "track_condition": "Good to Firm"
      }
    ],
    "meeting_date": "2026-07-15"
  }
}

About the Racing TV API

Meeting Schedules

list_meetings accepts a date parameter (ISO format YYYY-MM-DD) and an optional country filter (e.g. gb for Great Britain, ie for Ireland) to narrow results. The response returns an array of meeting objects, each containing track details, going conditions, and a nested list of races showing time, distance, class, and prize money. All meetings for the requested date are returned in a single response — no pagination handling required.

Detailed Racecards

get_racecard requires three inputs: date, a 24-hour time string in HHMM format (e.g. 1410), and a track slug as returned by list_meetings (e.g. catterick-bridge, bath). The response breaks into four top-level objects: race (metadata including class, distance, going, prize, pace bias commentary, and draw comment), meeting (track, date, going, TV channel), runners (one object per horse covering Timeform rating, form figures, weight, draw position, jockey, trainer, and breeding), and smart_stats (statistical insights when available).

Timeform and Pace Data

Each racecard includes Timeform-sourced fields at both the race and runner level. The race object carries an overall pace bias assessment and specific pace commentary alongside a Timeform verdict for the race. Individual runner objects include Timeform ratings and form strings. The last_winners array in the racecard response provides historical winners of that same race, useful for pattern analysis.

Coverage Scope

Meeting coverage spans UK and international fixtures accessible through Racing TV. The country filter on list_meetings supports ISO codes such as gb and ie. Track slugs needed for get_racecard are always derivable from list_meetings output, so the two endpoints are designed to be called in sequence.

Reliability & maintenanceVerified

The Racing TV API is a managed, monitored endpoint for racingtv.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when racingtv.com 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 racingtv.com 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.

Last verified
4h ago
Latest check
1/2 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
  • Pull daily UK race schedules filtered by country: gb to build a racing calendar widget.
  • Retrieve Timeform ratings and form figures from get_racecard runners to feed a selection model.
  • Extract pace bias and draw commentary from the race object to inform pre-race strategy notes.
  • Aggregate prize money and class data across meetings on a given date for competitive analysis.
  • Surface last_winners data from racecards to identify track-specialist horses.
  • Combine jockey and trainer fields from runner objects to compute trainer/jockey combination win rates.
  • Monitor going conditions across multiple tracks using meeting-level data from list_meetings.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 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.

Frequently asked questions
Does Racing TV have an official developer API?+
Racing TV does not publish a public developer API or documented data feed. This Parse API provides structured access to the meeting and racecard data available on racingtv.com.
What does `get_racecard` return for each runner?+
Each runner object includes Timeform rating, form figures, weight, draw position, jockey name, trainer name, and breeding details. The parent race object adds pace bias commentary, a draw bias comment, and a Timeform verdict covering the race as a whole.
Does `list_meetings` cover international fixtures beyond the UK and Ireland?+
Yes. Omitting the country filter returns all available meetings for the requested date, which can include international fixtures carried by Racing TV. Passing gb or ie narrows results to Great Britain or Ireland respectively.
Does the API return live in-running odds or starting prices?+
Not currently. The API covers racecard data, Timeform ratings, pace analysis, draw commentary, and historical winners. It does not include odds, starting prices, or live market data. You can fork this API on Parse and revise it to add an endpoint targeting Racing TV's odds or results pages.
Are post-race results and finishing positions available?+
Not currently. Both endpoints focus on pre-race information — schedules, runner details, and analytical content. Finishing positions and result data are not part of the current response schema. You can fork this API on Parse and revise it to target the results data for completed races.
Page content last updated . Spec covers 2 endpoints from racingtv.com.
Related APIs in SportsSee all →
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.
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.
racing.hkjc.com API
Access comprehensive horse racing data from the Hong Kong Jockey Club. Retrieve race results, detailed horse profiles including pedigree and form records, jockey and trainer season rankings, upcoming race meeting fixtures, and horse search by name.
bloodhorse.com API
Get comprehensive horse racing information including race results, stakes entries, horse profiles, and the latest news from BloodHorse.com. Search racing data, view detailed race information, and discover current racing leaders all in one place.
equibase.com API
Access comprehensive horse racing data from Equibase, including horse profiles, historical race results, track entries, post times, speed figures, and leader statistics for horses, jockeys, trainers, and owners.
neds.com.au API
Get up-to-date horse racing information from Neds, including upcoming races, event details, and past results. View which races are next to jump and access comprehensive race data all in one place.
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.
atg.se API
Access comprehensive horse racing data from ATG.se, including race calendars, detailed race information, horse profiles, starting lineups, and results. Retrieve up-to-date information on races, horses, drivers, betting pools, and outcomes.