Strava

About Strava

Strava's V3 API is a publicly available REST interface that gives developers access to Strava's dataset, including athletes, activities, clubs, gear, routes, running races, segments, segment efforts, streams, uploads, and webhook events. Access requires an OAuth-derived access_token sent with each request; a Strava API application only has access to a user's data once that user has authorized the application, though segment and segment leaderboard data is available to all applications. The API endpoint is https://www.strava.com/api, and requests use standard HTTP verbs (GET, POST, PUT, DELETE, HEAD).

The API applies per-application rate limiting: a default of 600 requests per 15 minutes and 30,000 requests per day, with usage and limits reported both on the application settings page and in HTTP response headers. Requests exceeding the limit return a 403 Forbidden response. Multi-item requests are paginated to 30 items by default, configurable up to 200 per page via the per_page parameter, and JSONP callbacks are supported for JavaScript applications. Dates follow ISO 8601, and routes are represented as Google-encoded polylines.

The page lists third-party client libraries maintained by the community for languages including Android, C#, Clojure, ColdFusion, Elixir, Erlang, Go, Haskell, iOS, Java, .Net, Node, Perl, PHP, Python, Ruby, Rust, and Scala. The API is intended for developers building applications that read or interact with Strava athlete and activity data, and is the same interface used internally by Strava's mobile applications.

Key features

• OAuth-based access to athlete activities, segments, clubs, gear, and routes data
• Segment leaderboards and effort tracking
• Activity data streams and GPS route polylines
• Webhook events for activity updates
• Photo/data upload endpoints for creating activities
• Pagination and JSONP callback support for API responses

Frequently asked questions