OrbTop

MarathonGuide Road Race Results Scraper

SPORTSEDUCATION

MarathonGuide Road Race Results Scraper

Extract finisher results from MarathonGuide.com — the largest US road-race results database, covering thousands of marathons and road races since the 1990s. Search by race name or supply a direct results URL to retrieve finish times, placements, age-group rankings, and runner details.

Data is sourced directly from the back.runzy.com JSON API that powers the MarathonGuide frontend, giving you clean structured records without browser automation.


What You Get

Each output record represents one finisher at one race:

Field Description
race_name Full race name (e.g. "Boston Marathon")
race_slug URL slug identifier (e.g. "boston-marathon")
race_year Year of the race
race_date Race date (YYYY-MM-DD)
race_location City, state, country
race_city / race_state / race_country Race location components
distance Distance label (e.g. "Marathon", "Half Marathon")
overall_place Overall finish position
gender_place Position within the runner's gender
division_place Position within the runner's age group
age_group Age group label (e.g. "M40-44", "F30-34")
runner_name Runner's full name
gender Runner's gender (M or F)
age Runner's age at time of race
finish_time Official finish time (chip time preferred)
chip_time Net/chip finish time
bib_number Bib number
city / state / country Runner's home location

Input Options

Search by race name

{
  "raceSearch": "Boston Marathon",
  "year": 2024,
  "gender": "all",
  "maxItems": 100
}
  • raceSearch — Search term matched against race names (partial matches work: "Chicago", "New York City Marathon")
  • year — Optional year filter. Omit to return results across all available years for matching races
  • gender — Filter by gender: all (default), M, or F
  • maxItems — Maximum total finisher records to return

Direct race URL

{
  "raceUrl": "https://www.marathonguide.com/races/run/boston-marathon/2024/results/",
  "maxItems": 500
}

Supply a full MarathonGuide results page URL. The actor extracts the race slug and year from the URL and fetches the finisher list directly, bypassing the search phase.


How It Works

The actor uses a two-phase approach:

  1. Race discovery — Searches the MarathonGuide API for races matching your query, filtering by year if specified. Returns a list of matching race occurrences with their slugs and years.

  2. Finisher pagination — For each discovered race, paginates through finisher results (up to 100 per API call) until maxItems is reached or all finishers are collected.

Both phases hit the back.runzy.com JSON REST API. No browser automation is required — the API is open and returns clean structured data.


Examples

Top 50 finishers at Boston Marathon 2024:

{
  "raceSearch": "Boston Marathon",
  "year": 2024,
  "maxItems": 50
}

Female finishers at Chicago Marathon 2023:

{
  "raceSearch": "Chicago Marathon",
  "year": 2023,
  "gender": "F",
  "maxItems": 200
}

All finishers for a specific race via URL:

{
  "raceUrl": "https://www.marathonguide.com/races/run/new-york-city-marathon/2023/results/",
  "maxItems": 50000
}

Notes

  • Results are ordered by overall place (fastest finisher first)
  • The MarathonGuide database covers thousands of US road races from the 1990s to present. Not all races have complete finisher data — some older events may have partial records
  • When raceSearch matches multiple races or multiple years, results are concatenated across all matches until maxItems is reached
  • Large races (Boston, Chicago, New York) have 20,000–50,000+ finishers; set maxItems accordingly and expect proportionally longer run times