Strava Pulls the Plug on their API: What This Means for Developers

Strava has made a sweeping decision to discontinue their API service as we know it, changing the ecosystem of third-party apps that have relied on their platform for years. Strava’s aggregation of wearable and app data made it the center of fitness tracking, powering third-party apps with activities, heatmaps, and leaderboards.

Let’s dive into what’s happening, why it matters, and what alternatives developers have.

What are the 3 major changes in Strava’s API agreement?

Strava is significantly restricting API access, cutting off certain apps and developers that don’t align with their new strategy. They’re introducing a stricter API agreement, with 3 main changes: 

 

1. Data Display Restrictions: Third-party apps can no longer display a user's Strava activity data to anyone other than the user themselves.
2. Prohibition on AI Usage: The new terms explicitly forbid third parties from using any data obtained via Strava's API for artificial intelligence, machine learning, or similar applications. 
3. Design and Functionality Constraints: Strava now requires third-party apps to maintain a design that complements Strava's distinctive look and feel.

What does this mean for third party apps?

Third party apps will face friction if they try to innovate using Strava’s data. Here are some explicit examples of companies that could face significant disruptions:

• Fitness Coaching Platforms such as Training Peaks and Final Surge depend on Strava data to provide training analysis and performance insights. 
• Public leaderboards and Challenge Apps such as VeloViewer and TrainerRoad which use public leaderboards and community-driven goals might lose their ability to display group performance metrics and shared activity data.
• Activity aggregators like Komoot, which visualize Strava data in 3D maps and in route planning features may struggle to offer the same user experience due to restrictions on data displaying.
• AI-powered platforms such as Final Surge or Xert will be hit hardest by the prohibition on using Strava API data for AI applications.
• Wearable Integrators such as Fitbod will need to ensure stricter compliance with Strava, which might limit their functionality scope.

What’s next for developers?

Strava’s restrictions are a wake-up call. Here’s how to future-proof your app:

• Diversify your data sources: By integrating with multiple wearable devices and fitness apps, companies can build a more robust and flexible ecosystem. You can expand your device coverage by incorporating APIs from popular wearable brands like Garmin, Fitbit, Apple Health, Samsung Health, and Oura to ensure a broad reach. Use multiple data streams to avoid service disruptions when one provider changes its policies.
• Trust the experts: build on platforms specifically engineered for aggregating health data instead of relying on generic solutions. Strive for excellence and access industry-leading latency and uptime with dedicated services that scale.
• Put users first: Earning user trust is more important than ever. Companies should focus on transparency and compliance by ensuring that all data collection and processing meet GDPR, HIPAA, CCPA, and other privacy regulations.

4. Why Terra API Offers a Better Model

Strava’s API changes highlight the importance of choosing flexible, future-proof solutions. Terra’s unified API provides a robust alternative for companies navigating these shifts. Here’s how Terra supports your needs:

With Terra, you:

• Own Your Data Flow: Access activity and health data from dozens of sources without dependency on a single aggregator.
• Future-Proof Your App: Terra is a specialist in that field, guaranteeing that you get standardised data from wearables, sensors and apps.
• Scale Seamlessly: Build once and integrate with all major devices, ensuring flexibility as the market evolves.

Watch the video below and learn how to connect to health and wearable data in 2 minutes with Terra API