Built for HYROX developers
Seasons, events, division results, athlete search, station splits, and precomputed stats. One versioned JSON API with a clear OpenAPI contract and predictable responses.
Versioned REST API · OpenAPI 3 · Bearer authentication · Catalog and live resolution
Pick an endpoint, press Send, and read the real response shape your app will receive — then copy it as cURL, JavaScript, or Python. These are recorded sample payloads, so nothing here needs a key.
Press Send to run the request.
Every field above is documented in the full OpenAPI spec.
Benchmarks & stats
Every event and division ships with precomputed statistics: counts, averages, medians, standard deviation and percentiles (p10 to p90) for the finish and all eight stations. One request, no crawling, no number crunching. Drag the slider to see how a goal time lands against a real field.
A finish is
Top %
faster than % of this field
p10
Median
p90
Skip the scraping and go straight to the product. Here are three things teams ship on day one.
Search by name, then pull race detail, result history, and station splits for a complete profile page.
{
"data": {
"name": "A. de Vries",
"division": "HYROX PRO",
"total_time_ms": 4021000,
"splits": { "skiErg_time_ms": 298000 }
}
}One request returns per station medians for an event, bucketed by division, gender, and age group.
{
"division_key": "HYROX PRO",
"sex": "M",
"age_group": "30-34",
"total_time": { "median_ms": 4098500 }
}Pull percentile benchmarks per division so athletes can set target splits and pacing plans.
{
"division": "HYROX",
"sex": "M",
"percentiles": {
"p50": { "total_time_ms": 4620000 }
}
}See every field in the documentation or explore the OpenAPI spec.
Built with the API
Real products and reference builds that ship on this API, from athlete facing simulators to leaderboards and coaching analytics.
Personalised HYROX training plans & race simulator
A coaching platform that turns a 10-question intake into a personal weekly plan and a race simulator. It uses the API's division benchmarks and per-station statistics to tell athletes exactly how their projected splits compare to the real field.
Your HYROX race, printed. A 30x40 cm poster of your splits versus the field.
Splitprint turns a HYROX result into a physical print. Athletes search their name and get a poster of their 8 runs and 8 stations, each compared against the median of their own field (gender, division and age group). Printed on 200gsm, shipped flat across Europe.
Type a goal time, get a station-by-station pacing plan
Let athletes enter a target finish and instantly see the split each station demands, plus the percentile that time lands in for their division, sex and age group.
Live rankings for any HYROX race, filterable in seconds
A leaderboard that lists every finisher for an event, filterable by division, sex, age group and nation, with cursor pagination for smooth infinite scroll.
A complete HYROX résumé for any competitor
Search by name, then render an athlete's every race, finish time and station splits on one profile page, including progression across seasons.
Find where an athlete leaks time versus the field
A coach dashboard that overlays an athlete's splits on division medians and percentiles, surfacing the stations to prioritise before the next race.
Drop-in finish-time widget for media & event sites
A lightweight embeddable widget that shows top finishers and division medians for a race, ideal for event organisers and sports media recaps.
Purpose built endpoints from season discovery to simulator benchmarks. Integrate once and focus on your product.
Browse seasons and list events with filters for season, country, and date range. Power race finders and event discovery.
Resolve events by slug, list divisions, and pull result tables for leaderboards, exports, and analytics.
Search by name, load race detail, fetch result history, and retrieve station splits for training and post race analysis.
Division level statistics and race simulator benchmarks with medians by gender and age group.
Responses include meta.data_source so you know whether rows came from synced catalog data or live resolution.
Contract first integration with /api/v1/openapi.yaml and Swagger UI at /docs.
Whether you ship leaderboards, training tools, or analytics, the API covers the full HYROX data model.
Division results, rankings, and finish times for live and post race experiences across the full HYROX calendar.
Search athletes, pull split times, and compare station performance against field medians.
Precomputed stats by division, gender, and age group for simulators, pacing tools, and performance dashboards.
A focused surface area. Every route documented in OpenAPI.
| Method | Endpoint | Description |
|---|---|---|
| GET | /v1/seasons | List all HYROX seasons |
| GET | /v1/events | List events with season and country filters |
| GET | /v1/divisions/{id}/results | Paginated division results and rankings |
| GET | /v1/athletes/search | Search athletes by name |
| GET | /v1/athletes/{id}/splits | Station split times for a race |
| GET | /v1/stats/divisions/{id} | Precomputed stats by division, gender, and age group |
| GET | /v1/simulator/benchmarks | Race simulator benchmark data |
Authorization: Bearer … on each request.
GET /api/v1/athletes/{id}/splits
returns all eight runs and all eight stations individually timed for a single race, so you can show
exactly where an athlete gained or lost time. Search by name to get the race id, then ask for its
splits — two requests from a name to a full station breakdown.
HYROX_MEN. Advanced split data is
the median per station for one specific race, broken down by division, gender and age group, so an
athlete is compared against the people who actually raced alongside them. Division benchmarks are on
every plan; advanced split data is on the Scale plan.
meta.data_source.
GET /api/v1/events/{slug}/ingest-status. It
reports whether the rankings are still coming in, how many finishers are stored, and whether the field
splits are queued, running or done, so you never have to infer it from the shape of a stats payload.
A race weekend runs several days and each division races on one of them, so the response also carries
that division's own race day and whether its results are due yet — an empty ranking on the Saturday
is a Sunday division, not a stalled ingest.
429 with a
Retry-After header telling you exactly how long to
wait. Your current limit is on
GET /api/user. There are separate protections
against bulk extraction of the whole catalogue, set so that an application serving real users does not
meet them.
GET /api/v1/athletes/search. Each hit carries a
race id for that one performance and a
person_ref that ties their performances together,
so you can go from a name to a full race history and then to station splits without guessing at ids.
season,
country and date filters, so you ask for the
slice you want. Full finisher lists use a cursor, which stays fast on the deepest page of the biggest
race rather than degrading the further in you go.
Cache-Control and an
ETag; a finished race is marked cacheable for a
week because its results never change again. Send the ETag back as
If-None-Match for a
304 and no body.
Subscribe in minutes. Cancel anytime from your account.