Horse Racing Pulse API
Pricing
from $20.00 / 1,000 api requests
Horse Racing Pulse API
Live PMU horse-racing odds as an always-on HTTP API (Server Actor): GET /races for every race open for betting with odds per runner, GET /movers for steamers and drifters over the last N minutes. 19 filters, answers in milliseconds from a once-a-minute cache.
Pricing
from $20.00 / 1,000 api requests
Rating
0.0
(0)
Developer
0xGollum
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
6 days ago
Last modified
Categories
Features
Share
Horse Racing Pulse API — live PMU odds in one HTTP call
Your bot needs the odds of the 14:15 at Vincennes now, not after a 2-minute scraper run. This Server Actor stays awake and answers from a cache that refreshes every race still open for betting once a minute: a GET returns live odds per runner in milliseconds, and /movers tells you which horses the money is moving on.
What a call returns
GET /movers?countries=FRA&window_minutes=10
{"updated_at": "2026-11-11T07:45:24+00:00","window_minutes_used": 10.0,"mover_count": 1,"movers": [{"signal": "steamer", "trigger": "relative","hippodrome": "LYON LA SOIE", "race_code": "R4C2", "race_name": "OURASI","horse_num": 6, "horse_name": "JUAN LES PINS","current_cote": 16.0, "previous_prob_pct": 2.5, "current_prob_pct": 6.25,"prob_change_pct": 3.75, "relative_change_pct": 150.0}]}
GET /races returns every open race (venue, R4C2 code, start time in Unix ms, discipline, distance, prize, runners) with a runners_list sorted favourite first: number, name, jockey/driver, decimal odds, implied probability.
Endpoints
| Endpoint | What you get | Billed |
|---|---|---|
GET /races | Races open for betting, odds per runner | 1 api-request |
GET /movers | Steamers and drifters over the last window_minutes (1-90, default 10) | 1 api-request |
GET /health | Cache age, runners tracked | free |
GET / | This list of endpoints | free |
A request that fails (warming up, bad parameter) is never billed.
/movers parameters: window_minutes, threshold_pct (implied-probability points, default 5), relative_pct (relative change, default 30 %; catches the 50/1 → 20/1 outsider that only moves 3 points), limit (default 25). The server keeps 90 minutes of snapshots in memory, so you don't need to schedule anything to see movement.
Filters (query parameters, same as Horse Racing Pulse)
Lists are comma-separated: ?countries=FRA&disciplines=PLAT,HAIE&meetings=CHANTILLY.
countries, meetings (partial, accent-insensitive), disciplines (PLAT, HAIE, STEEPLECHASE, ATTELE, MONTE, CROSS), categories (HANDICAP, GROUPE_I…), surfaces, going, age_conditions, sex_conditions, track_directions, min_distance_m / max_distance_m, min_prize_eur / max_prize_eur, min_runners / max_runners, start_after / start_before (HH:MM, filter_timezone default Europe/Paris), min_odds / max_odds (runner level), max_races (/races, default 20).
How to call it
Copy the URL from the Server tab of this Actor and send your Apify token in a header:
curl -H "Authorization: Bearer $APIFY_TOKEN" \"https://<server-url>/movers?countries=FRA&window_minutes=15"
import httpxr = httpx.get("https://<server-url>/races", params={"disciplines": "PLAT", "max_races": 5},headers={"Authorization": f"Bearer {token}"})
The first call after a quiet period wakes the server (a few seconds), then answers are immediate. /movers needs a few minutes of history after a wake-up: until then it says so and uses the longest window available.
Classic run
Started from the Input tab like any Actor, it takes one snapshot of the open races and writes it to the dataset (same filters). Use it to test the filters before wiring the API.
Data source and limits
Odds come from PMU's public programme (French tracks plus the foreign tracks PMU takes bets on). Pari-mutuel odds float with the pool until the off, so morning odds move a lot on thin pools: raise threshold_pct or narrow start_after / start_before to focus on races about to start. Races that have started or closed disappear from the cache. Not affiliated with PMU. Odds are informational, not betting advice.
Need scheduled runs with history kept between runs and hidden form patterns per horse? See Horse Racing Pulse (same filters, batch mode).