Connect race events
to your trading stack.
Implementation detail for sportsbook engineers and quant teams: integrate live timing, race-control events and replay into your existing systems. Review feed contracts, eligible events and delivery behavior before connecting your pricing operation.
What sportsbook pricing and trading teams build on RaceHooks
In-play pricing & automated trading
Position, interval, sector times, tyre state, and pit activity arrive as they change, so your model reprices on the event rather than on a timer. A safety car is the sharpest repricing moment in the race and it reaches you as a typed message, not as a diff you have to spot.
Pre-race market setup
Grid penalties and steward decisions publish before lights out and move an outright market on their own. Take them as structured events with the driver, the offence, and the penalty already parsed — a grid drop applied to your starting-position assumptions the moment it is official.
Weather-driven repricing
Rain is the single largest variance event in an F1 race, and it starts locally. Onset and clearing fire as discrete events off circuit-side readings, with the full weather series behind them — so a wet-race position turns over on the measurement, not on a forecast you refreshed five minutes ago.
Backtesting & research
Replay a real session at any speed from 0.1× to 120× and drive your pricing logic with the exact payloads a live race would have sent, in the order it sent them. Behind that sits results back to 1950, with lap timing, stints and pit stops subject to era coverage for the offline fit.
One payload, straight onto the screen
Connect the race state to your pricing workflow: the event that triggers a review, the running order behind your line, and the delivery path into your stack.
Route grid penalties, steward decisions, and race control straight into the desk. Because it is push, the alert fires on the decision — not on your next poll.
The ordering is the product. A poll loop learns about a safety car on its next tick; a push subscriber learns about it when race control says so.
Example interfaces, rendered from the fields above: your product, your design system. Nothing here is a template you have to adopt.
The endpoints that build it
Every route is Bearer-authenticated and versioned under /v1. Base URL https://api.racehooks.io/v1.
| Method | Path | What it gives you |
|---|---|---|
| POST | /v1/webhooks | Subscribe an endpoint to a feed. One endpoint can carry the whole live catalog; filter by driver at subscription time when a strategy only trades a subset. |
| GET | /v1/stream | Server-Sent Events over one long-lived connection — the path for a desk behind a firewall with no public webhook host. |
| GET | /v1/simulate/sessions | Replayable sessions. Prepare one and it delivers to your real endpoint at any speed from 0.1× to 120× — the same payloads, same order, no race day required. Developer unlocks 10 distinct current-season sessions; the full archive is Custom. |
| GET | /v1/historical/:season/:round/laps | Lap-by-lap times for supported seasons and sessions — the offline fit behind a live model. |
| GET | /v1/historical/:season/:round/stints | Compound and stint plan per driver, with pitstops on the sibling route for the stop that ended each one. |
| GET | /v1/data/races/:raceId/qualifying | Qualifying result for a round — the starting-grid input before grid penalties are applied. |
race.grid-penaltyGrid drops and pit-lane starts as the stewards publish them — the pre-race picture, before lights out.regulatory.stewards-decisionParsed steward decisions: driver, offence, penalty, and the session it applies to.race-control.messagesSafety car, VSC, red flag, and track status in race control's own wording — the sharpest repricing moments in the race.timing.dataPosition, leader gap and interval, lap and sector times — the state a live price is set against.events.race40+ synthesized events including overtakes, retirements, and pit stops, each carrying the driver it belongs to.weather.rain-onsetFires when rainfall begins at the circuit. weather.rain-cleared closes it; weather.data-series is the trend behind both.pit.stopsStops as they complete, with the stationary time on pit.lane-times — a slow stop is a position, and a position is a price.Developer includes all 29 live data feeds, not just the ones above; the remaining 26 in the 56-feed catalog are the Custom analytics feeds. Every id, cadence, and payload schema is documented.
Three ways the data reaches you
Pick per integration. You can run all three against one API key. Webhook and SSE frames are both counted as deliveries (Free pauses at its monthly limit; Developer has no delivery limit); REST reads count against the request rate limit instead.
Webhook
Push · defaultRegister an HTTPS endpoint and subscribe it to feeds. RaceHooks POSTs events as source updates arrive. Every payload is HMAC-SHA256 signed, retried with exponential backoff on failure, and every attempt is logged in your console with headers, status, and latency.
POST /v1/webhooks
{ "webhookUrl": "https://your-app.com/hook",
"feedId": "events.race" }SSE stream
Push · no public URLOpen one long-lived connection and read frames as they arrive — no public webhook server to host or expose. Each frame is `event: <feedType>` + a JSON `data:` line, with a ping every 30s so proxies hold the connection open. Auth by Bearer header, or `?token=` for browser EventSource, which cannot set headers.
GET /v1/stream?feeds=raceevent,timingdata
Authorization: Bearer $TOKENREST
Pull · on demandQuery completed and reference data directly whenever you need it: results, standings, laps, stints, pit stops, and the segment endpoints above. Use it to backfill history, hydrate a new user, or reconcile after an outage rather than to follow a live session.
GET /v1/historical/2026/16/results
Authorization: Bearer $TOKENTest the whole thing on a quiet Tuesday
Simulate replays a real current-season session through your own webhooks at any speed from 0.1× to 120×. Your integration receives the exact payloads it would in a live race (real data, known result) so you can validate books logic end to end before a live session ever runs. Free includes 5 sessions, Developer 10; Custom replays the full archive.
How Simulate works →What the ML layer adds for books
Everything above is the input side: what happened, typed and fast, for a desk that builds its own prices. Custom adds the priced surfaces — our own distributions over the same race, so you can trade them or mark your own model against them. Model outputs publish only on supported sessions, schedules and eligible race states. Review the output contracts and evaluation scope with us.
Position distributions & race odds
analytics.race-odds carries a full position distribution per driver from a continuous-time Markov model — win, podium, and points probabilities recomputed as the race moves, not a static pre-race line.
Championship & standings projection
standings.projection simulates the title race from the current order; analytics.championship-probability resolves both championships post-race. GET /v1/data/seasons/:year/championship-probability is the pull-side equivalent.
Winning margin & gap projection
analytics.winning-margin projects the P1–P2 gap with percentile bands, and analytics.gap-projection does the same to the leader for every car — the margin and match-up markets, priced.
Head-to-head and position-at-lap research
GET /v1/analytics/h2h and /v1/analytics/position-at-lap answer the two questions a research desk asks most, over the historical corpus rather than one race — plus full-archive replay for a backtest that is not capped at the current season.
Bring us your next race decision.
Tell us what you need to decide. We’ll walk through the relevant models, outputs and scope of an evaluation.