Adapting Your Integration to Strava's API Changes Since 2024

What actually changes#

The changes are less about new endpoints and more about program terms, display rules, and how third-party data can be used. As of 2026, the high-level shifts are below — verify each against the live agreement before acting, because Strava's docs and terms move. The Strava program changes we track are also listed by month in the monthly digest.

The practical impact concentrates in a few places. Athlete permission and consent are required and must be visible in your UI. Data display and retention are constrained by the current terms, so a field you store or render today may need to be reformatted or dropped. And if Strava data currently flows through an aggregator or intermediary, that path may not comply — a consequential risk for anyone who reaches Strava indirectly. For target-integration setup details see the Strava API integration guide, and if you decide the terms no longer fit your product, weigh the Strava API alternatives.

The migration, step by step#

This is an adaptation of an existing integration, so the sequence is audit-first, then reconcile architecture, then re-enroll. Run your current integration in parallel while you validate the changes.

1. Re-read the current agreement. Open the live Strava API Agreement, Developer Program terms, and API Policy — they supersede any summary, including this page.
2. Refresh the Developer Program form. Complete or update it with current screenshots of every surface where Strava data appears, plus the "Connect with Strava" button.
3. Audit stored and displayed fields. Check every Strava field you store or render against current terms; remove or reformat anything non-compliant and fix attribution and branding.
4. Confirm athlete consent. Verify your permission and consent UX meets the current athlete-permission requirements and is reflected in the UI.
5. Check the intermediary/aggregator path. If Strava data flows through an aggregator or intermediary platform, verify that path is still permitted; plan a direct integration if it is not.
6. Re-check rate limits and webhooks. Reconcile your rate-limit handling and the one-subscription-per-app webhook constraint against your architecture — see why Strava webhooks stop firing if events stop arriving.
7. Confirm the subscription requirement. Strava's getting-started guide says "A Strava subscription is a prerequisite for creating an app." Its API Policy can also require an active Strava subscription of the developer or specified end users on the Standard Tier, so check which applies to your app before you budget.
8. Choose your tier. Decide Standard vs Extended Access based on athlete reach, and apply for Extended Access if you need it.

Gotchas and how to keep users connected#

The intermediary-platform restriction is the one that can force real rework: if you reach Strava through an aggregator, confirm the wording of the current terms before assuming your path survives, and plan a direct rebuild if it does not. Athlete grants and consent are not something you can silently carry over — if you change how you collect consent, plan for athletes to re-authorize. The one-subscription-per-app webhook limit means you cannot spin up parallel subscriptions freely, so coordinate any migration around that single channel. And because tier caps, fees, effective dates, and rate limits have all shifted since 2024, do not build against any specific number from memory.

Keep your existing integration live while you reconcile these items, and cut over only once you have confirmed compliance against the current agreement. Realistically this is a compliance-and-architecture pass, not a rewrite of your core data flow — but the intermediary and subscription changes can escalate it into a direct re-integration, so scope it after you have read the live terms. When in doubt, verify the current Strava developer agreement and API Policy.