Running

Overview

The Running domain tracks your Strava activity, including distance, pace, elevation, splits, gear, and personal records.

Strava imports every activity type, not just runs: rides, walks, hikes, weight training, and the rest all land here. Each activity carries the sport type, its city and state (reverse-geocoded from the start coordinates), and a route polyline for mapping. Running-specific stats such as pace, personal records, and streaks are computed over run activities only.

Activities sync daily, with new activities arriving in real time via Strava webhooks. Browse every endpoint in the API reference.

Charts

Several endpoints return chart-ready series for plotting: cumulative distance, pace trend, time-of-day distribution, and elevation gain over time.

Filtering

The activities endpoint supports filtering by:

• year: filter to a specific year.
• type: workout type (default, race, long_run, etc.).
• city: filter by city name.
• min_distance / max_distance: distance range in miles.
• sort: sort field (date, distance, pace, elevation).
• order: asc or desc.
• Standard date filters (date, from, to).

Year in review

For a per-year breakdown, use GET /running/stats/years/:year. It returns year-specific stats such as total runs, distance, elevation, and pace for the requested year.

Images

Running activities carry map artwork generated from Strava map tiles. See Images for the source and fallback details.

From Claude

You can also explore your running history from Claude. Set up the MCP server and ask in natural language, like how far you ran last month or for a year-over-year pace trend. Claude answers most questions by querying the database directly with SQL.