Httpswww APIhttpswww.sportinglife ↗
Access Sporting Life horse racing racecards by date and get detailed runner data — trainer, jockey, form, odds, and more — via two structured endpoints.
What is the Httpswww API?
The Sporting Life Racecards API exposes horse racing data across 2 endpoints, covering daily race listings and per-race runner details. get_racecards returns all meetings and races for a given date, while get_race_detail delivers 10+ fields per runner including trainer, jockey, weight, draw, official rating, forecast odds, spotlight commentary, and lifetime form — everything needed to build race analysis or betting tools.
curl -X GET 'https://api.parse.bot/scraper/bedce0aa-e449-40ef-af7c-ab1c6c571914/get_racecards?date=2026-10-06' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns all race meetings and their races for a given date. Each race includes venue, time, title, class, distance, going, surface, and runner count. Use race_id from the results to fetch detailed runner information via get_race_detail.
| Param | Type | Description |
|---|---|---|
| daterequired | string | Race date in ISO format YYYY-MM-DD (e.g. 2026-08-22). |
{
"type": "object",
"fields": {
"date": "string — the requested date",
"meetings": "array of meeting objects, each containing venue, country, going, surface, and a races array"
},
"sample": {
"data": {
"date": "2026-08-22",
"meetings": [
{
"date": "2026-08-22",
"going": "Good to Soft (Good in places)",
"races": [
{
"age": "3YO plus",
"name": "Sky Bet Strensall Stakes (Group 3)",
"time": "12:50",
"going": "Good to Soft (Good in places)",
"race_id": 934439,
"surface": "TURF",
"distance": "1m 177y",
"race_class": "1",
"race_stage": "WEIGHEDIN",
"has_handicap": false,
"runners_count": 11
}
],
"venue": "York",
"country": "England",
"surface": "Turf"
}
]
},
"status": "success"
}
}About the Httpswww API
Daily Race Listings
The get_racecards endpoint accepts a single date parameter in YYYY-MM-DD format and returns all race meetings scheduled for that day. Each meeting object includes the venue, country, going, and surface, along with a nested races array. Each race entry carries its title, class, distance, scheduled time, and runner count. The race_id values returned here are the keys for fetching full runner details.
Per-Race Runner Detail
Pass a race_id to get_race_detail to retrieve the full racecard for a single race. The response includes race-level fields — name, date, time, venue, going, surface, distance, and age restriction — alongside a runners array. Each runner object contains horse_name, trainer, jockey, weight, draw, official_rating, forecast_odds, commentary (Sporting Life's spotlight text), form (recent run history), and headgear. This is the primary payload for building pre-race analysis.
Coverage and Data Shape
Data is organized around the British and Irish racing calendar as covered by Sporting Life, though the country field on meeting objects indicates international fixtures also appear. Going and surface are reported at the meeting level in get_racecards and confirmed at the race level in get_race_detail. There is no pagination — get_racecards returns all meetings for the requested date in a single response.
The Httpswww API is a managed, monitored endpoint for httpswww.sportinglife — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when httpswww.sportinglife 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 httpswww.sportinglife 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?+
- Display a daily race schedule grouped by venue, distance, and going conditions for a racing information site.
- Build a pre-race form guide by pulling
form,official_rating, andcommentaryfor every runner in a race. - Compare forecast odds across runners in a single race to flag market movers before the off.
- Aggregate trainer and jockey statistics by parsing
trainerandjockeyfields across multiple race results. - Filter races by
surfaceordistanceto feed a machine-learning model for race prediction. - Power a racecard widget that shows draw, weight, and headgear for each horse in a selected race.
| 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 Sporting Life have an official developer API?+
What does get_race_detail return for each runner, and does it include live or final odds?+
get_race_detail returns forecast_odds for each runner, which reflects pre-race forecast prices rather than live in-play or SP (starting price) odds. Other runner fields include horse_name, trainer, jockey, weight, draw, official_rating, form, headgear, and a commentary spotlight string.Does the API return historical race results or finishing positions?+
Is data available for international races outside Britain and Ireland?+
country field on each meeting object in get_racecards responses indicates that international fixtures appear alongside British and Irish meetings when Sporting Life lists them. Coverage depth for international fixtures may be narrower than for domestic meetings, and not all countries will consistently appear on every date.Does the API cover ante-post markets or only race-day cards?+
get_racecards endpoint is date-driven and returns races scheduled for a specific day; ante-post or future-entry markets are not exposed. You can fork this API on Parse and revise it to add an endpoint targeting ante-post race listings.