Racing
Horse racing APIs: providers, data and integration guide
A horse racing API can supply structured meeting, race and runner information for a publication, racecard website or results service. UK and US racing involve different tracks, schedules and commercial data arrangements. This guide compares the relevant suppliers in our existing list and explains the checks needed before assuming a general racing product supports your territories, race types and required fields.
By Sarah MitchellUpdated
Sources last checked
Short answer
BettorServe advertises horse racing publishing experiences, and Goalserve lists a dedicated horse racing feed. They are relevant starting points from our current provider list, not proof that every racecard field or every UK and US track is included. Request current samples, exact territorial coverage and written publishing rights for the races and outputs your website will use.
Provider shortlist for Horse racing
The score shown is our general editorial website-integration fit score for the provider overall. It is not a Horse racing-specific rating.
- Featured placement
BettorServe: Featured horse racing publishing option
Data / widget product
Horse racing widgets and API discussions; confirm racecard fields, tracks and supported markets.
Sources: [1] BettorServe official 11-sport widget and API catalogue · Product page
Goalserve: Horse racing feed package
Data / widget product
A dedicated racing package is advertised; verify track coverage, history and required fields.
Sources: [2] Goalserve official sport-specific API packages · Product page
This is a commercially oriented comparison site. We may earn a commission through eligible partner links, at no extra cost to you. BettorServe is our featured first listing. Commercial relationships and featured placements should be considered alongside the product details, and you should confirm current terms directly with a provider before purchasing.
Start with country, race type and use case
Write a brief that identifies countries, tracks, race types and seasons. A UK racecard site, a US results archive and a bookmaker comparison are different products. Flat and jump racing also need clear categorisation. Do not assume that a supplier saying horse racing has the same depth for every meeting in both markets.
The API directory separates horse racing from motorsport APIs. They share a racing label but not an event model or licence. Within horse racing, distinguish meeting schedules, racecards, live changes, results and prices. Ask which of these resources the proposed service actually supplies and which must come from another authorised source.
Sources: [1] BettorServe official 11-sport widget and API catalogue, [2] Goalserve official sport-specific API packages
Relevant horse racing provider options
BettorServe describes horse racing publishing experiences as part of its sports offering. The BettorServe review explains the widget-led approach for websites adding information alongside articles. Test the actual racing display, including long runner names and mobile layouts, and ask which fields are available to a custom integration rather than only within the finished embed.
Goalserve advertises a dedicated horse racing feed, with track and historical coverage requiring direct confirmation. Read the Goalserve review before requesting sample race records. This guide deliberately presents a shorter supported shortlist instead of assigning all ten general sports providers to racing without evidence that their checked catalogues offer the required product.
Sources: [1] BettorServe official 11-sport widget and API catalogue, [2] Goalserve official sport-specific API packages
Racecards need stable relationships and change handling
A racecard can connect a meeting, race, runners and participants such as jockeys or trainers where licensed fields exist. Define which fields your website genuinely needs, then ask for data definitions and examples. Distance, surface, conditions and scheduled time should be treated as structured information rather than parsed from an unverified text label.
Non-runners and changed declarations require updates to an existing race, not a duplicate event. Preserve provider identifiers and distinguish scheduled information from confirmed results. Where a field is unavailable, display that honestly. Do not fabricate runner attributes or assume a missing value means a horse has no relevant prior record.
Sources: [2] Goalserve official sport-specific API packages, [1] BettorServe official 11-sport widget and API catalogue
Results, race status and historical information
A result resource should be assessed independently of a racecard resource. Ask how the provider marks provisional and confirmed outcomes, withdrawals, abandoned races and later corrections. A website should not declare an official result solely because an early finishing order appears in a response or an embedded display.
Historical records need equally precise scope. Confirm countries, tracks, seasons and whether retained records include the same fields as current cards. If your editorial product calculates form summaries, document the included races and data limitations. A partial archive should not be presented as a complete account of a runner's career or future performance.
Racing odds are a separate data requirement
If your site compares prices, ask specifically about bookmaker coverage, market definitions and timestamps. A racecard feed does not automatically supply odds, and a bookmaker price does not establish access to licensed racecard fields. Keep the source and purpose of each resource clear when combining them in one page.
Explain whether the displayed figure is a current retrieved price, a historical price or another defined value. Do not imply guaranteed availability at a destination. Affiliate links need clear disclosure, and readers should verify market terms directly. General provider ratings on this website describe editorial fit, not independently tested horse racing accuracy or profitable betting performance.
Sources: [1] BettorServe official 11-sport widget and API catalogue, [2] Goalserve official sport-specific API packages
Racecard publishing rights and an evaluation plan
Describe your intended UK and US audiences, commercial model, public outputs and retention policy when requesting a licence. Numerical race data, runner imagery, silks, photographs and video can have different permissions. A provider's ability to deliver a field does not automatically grant unrestricted redistribution or reuse across client sites.
Test a full race-day workflow from scheduled meeting to declared runners, changes and corrected final results. Cache only within the agreement, secure credentials and monitor freshness rather than silently showing stale information. The golf API guide illustrates another event-based comparison, but horse racing requires its own sources, terminology and commercial checks.
Sources: [2] Goalserve official sport-specific API packages, [1] BettorServe official 11-sport widget and API catalogue
Frequently asked questions
Which providers in this directory advertise horse racing?
BettorServe lists horse racing publishing experiences, and Goalserve advertises a dedicated horse racing package. Confirm the required tracks, countries and fields directly. This supported shortlist is intentionally narrower than the site’s overall ten-provider comparison.
Sources: [1] BettorServe official 11-sport widget and API catalogue, [2] Goalserve official sport-specific API packages
Does one horse racing API cover both the UK and US?
That depends on the selected product and agreement. Ask for a current track and territory list, plus race-type and historical detail. A generic racing description is not proof of complete racecards, live changes or results in both countries.
Will a racecard feed automatically include bookmaker odds?
No. Treat racecards, results and price markets as distinct requirements. They may be supplied together or under separate products and conditions. Confirm bookmaker coverage, market definitions and update times before promising an odds-comparison feature on your website.
Sources: [1] BettorServe official 11-sport widget and API catalogue, [2] Goalserve official sport-specific API packages
Can I store horse racing results indefinitely?
Only if the licence permits the retention and use you intend. Ask about historical archives, public display, redistribution and any asset restrictions. Access to current records does not automatically establish an unlimited right to retain and republish the entire dataset.
How should non-runners and abandoned races be handled?
Use the provider’s documented identifiers and status fields to update existing records. Keep withdrawals and abandoned events distinct from normal completed results. Show missing information clearly, and do not infer an official outcome simply from an incomplete or provisional response.
Sources: [2] Goalserve official sport-specific API packages, [1] BettorServe official 11-sport widget and API catalogue
Official sources
Checked . Provider pages can change; confirm details before you buy.
- BettorServe official 11-sport widget and API cataloguehttps://bettorserve.com/
- Goalserve official sport-specific API packageshttps://www.goalserve.com/en/sports-data-api