RaceMetrics APIracemetrics.co.uk ↗
Access RaceMetrics rating leaderboards, biggest 7-day risers, and trainers-in-form tables for horses, jockeys, trainers, and sires via a simple REST API.
What is the RaceMetrics API?
The RaceMetrics API exposes 3 endpoints covering the published rating leaderboards, weekly rating movers, and rolling trainer form tables from racemetrics.co.uk. The get_rating_rankings endpoint returns the top-25 ranked participants for any of four categories — horses, trainers, jockeys, or sires — including each participant's rating, run count, and profile ID. Data is structured for direct integration into horse racing dashboards, betting tools, and form analysis workflows.
curl -X GET 'https://api.parse.bot/scraper/20477beb-c9b9-4043-a234-5b93b5a23a45/get_rating_rankings?category=horses' \ -H 'X-API-Key: $PARSE_API_KEY'
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 racemetrics-co-uk-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: RaceMetrics SDK — ratings, risers, and trainers in form."""
from parse_apis.racemetrics_co_uk_api import (
RaceMetrics, RankingCategory, FormWindow, InputFormatInvalid,
)
client = RaceMetrics()
# Top-rated horses leaderboard
try:
for horse in client.rankings.list(category=RankingCategory.HORSES, limit=5):
print(f"#{horse.rank} {horse.name} rating={horse.rating} runs={horse.runs} last_run={horse.last_run}")
except InputFormatInvalid as e:
print(f"Invalid category: {e.message}")
# Biggest 7-day rating risers across all categories
riser = client.risers.list(limit=1).first()
if riser is not None:
print(f"Top riser: {riser.name} ({riser.category}) +{riser.rating_change_7d}")
# Trainers in form over the last 14 days
for t in client.trainers.list(window=FormWindow.DAYS_14, limit=5):
today = f", runners today: {t.runners_today}" if t.runners_today is not None else ""
print(f"#{t.rank} {t.name} W{t.wins}/{t.runs} ({t.win_percent}%) P/L SP: {t.profit_loss_sp}{today}")
print("exercised: rankings.list / risers.list / trainers.list")
Returns the published top-25 leaderboard of RaceMetrics ratings for one participant category (horses, trainers, jockeys or sires). Each row carries the rank, name, the site's participant profile id, the rating (1500 is average), the number of runs behind the rating and the last-run date as the site prints it (day and abbreviated month, e.g. '13 Sept'). Ratings are refreshed daily each morning. One request per call; the leaderboard is a fixed top 25, so there is no pagination.
| Param | Type | Description |
|---|---|---|
| categoryrequired | string | Participant category whose rating leaderboard is returned. An unrecognised value is rejected without a request to the site. |
{
"type": "object",
"fields": {
"count": "integer number of ranking rows returned",
"category": "the category echoed back, matching the requested value",
"rankings": "array of leaderboard rows, ordered by rank ascending"
},
"sample": {
"data": {
"count": 25,
"category": "horses",
"rankings": [
{
"name": "Jonbon",
"rank": 1,
"runs": 20,
"rating": 1709,
"last_run": "12 Mar",
"profile_id": "354546"
},
{
"name": "Dinoblue",
"rank": 2,
"runs": 19,
"rating": 1701,
"last_run": "1 May",
"profile_id": "363239"
}
]
},
"status": "success"
}
}About the RaceMetrics API
Rating Leaderboards
get_rating_rankings accepts a required category parameter — horses, trainers, jockeys, or sires — and returns up to 25 rows ordered by rank. Each row includes the participant's name, their RaceMetrics profile ID, their numeric rating (where 1500 represents the average), the number of runs used to calculate that rating, and the date of their last run. The category field is echoed back in the response alongside a count of rows returned.
Rating Risers
get_rating_risers returns the site's 'biggest risers — last 7 days' table with no input parameters required. Each row in the risers array includes the participant's name, their category label as displayed on the site (Sire, Trainer, Jockey, or Horse), and the magnitude of their rating gain over the prior seven days. This endpoint is useful for identifying in-form participants across all categories in a single call.
Trainers in Form
get_trainers_in_form accepts a required window parameter of either 7 or 14 days and returns a ranked list of trainers by recent performance. The 7-day response includes runs, wins, win percentage, and level-stakes profit/loss to a 1-unit stake at starting price. The 14-day response additionally carries placed count, place percentage, and place-level profit/loss. The window_days integer field in the response confirms the window applied.
The RaceMetrics API is a managed, monitored endpoint for racemetrics.co.uk — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when racemetrics.co.uk 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 racemetrics.co.uk 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.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a weekly horse racing newsletter highlighting the top-rated horses and jockeys from the leaderboard.
- Track trainer win percentages and level-stakes P&L over 7- and 14-day windows for betting model inputs.
- Identify cross-category rating movers using the risers endpoint to spot in-form sires and trainers before they become widely discussed.
- Populate a racing dashboard with ranked trainer, jockey, and sire ratings updated from the latest leaderboard data.
- Monitor a specific trainer's rank and run count over time by querying the trainers category leaderboard regularly.
- Filter the trainers-in-form 14-day table by place percentage to surface trainers whose horses run consistently in the frame.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 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.
Does RaceMetrics have an official developer API?+
What does the `get_rating_rankings` endpoint return for the 'horses' category versus others?+
category field in the response echoes back whichever value you passed. The leaderboard is capped at 25 rows per category.Does the API cover historical rating data or full rating histories for individual participants?+
Can I retrieve trainers-in-form data for windows other than 7 or 14 days?+
window parameter on get_trainers_in_form accepts only 7 or 14; any other value is rejected before a request is made. You can fork this API on Parse and revise it if the source adds additional window options in the future.Does the risers endpoint distinguish between horses, trainers, jockeys, and sires?+
risers array includes a category label as printed by the site — for example Sire, Trainer, or Jockey — so you can filter the array client-side by participant type after a single call.