What was the Strava API change?

Strava restricts API access while fighting AI scraping

Strava is rolling out major changes that affect how developers and third parties access its data, with the stated goal of reducing automated scraping—especially by AI-related tools.

The company’s move includes:

• A paid API tier: Strava is adding a $11.99 monthly fee for developer API access.
• Authentication walls: Public profiles and fitness club listings are being moved behind authentication, so they’re no longer broadly accessible without signing in.

The timing matters because Strava has faced criticism about how its community data can be harvested at scale. With fitness and location data valuable to both researchers and scammers—and increasingly useful for machine learning and recommendation systems—Strava says the updated access rules are meant to curb the automated collection patterns that can degrade user trust and privacy.

What this likely means for developers:

• Integrations that previously relied on freely available endpoints will need to switch to the paid API and comply with Strava’s terms.
• Scraping approaches—particularly those designed to collect public pages without authorization—may stop working or become less effective once content requires login.

For users and the broader tech ecosystem, this is another example of platforms tightening control of data flows as generative AI and analytics tools expand. Strava’s stance suggests that even for “public” content, platforms may increasingly require authenticated access and enforce commercial terms to limit unstructured data harvesting.

It also signals a continuation of a wider trend: platforms using authentication, rate limits, and API monetization to separate legitimate developer use from mass extraction.