Developers & API

Hello, the following API appears to no longer be returning latlng.  I believe I ran this same URL a few weeks ago and did receive latlng in the results.“https://www.strava.com/api/v3/activities/<ACTIVITY_ID>/streams?access_token=<ACCESS_TOKEN>&keys=time,latlng&key_by_type=true” When I convert the response to json, the structure of the response appears as follows (I put in the “...”){'distance': {'data': [0.0, 0.0, 9.2, ... 4438.1, 4440.6], 'series_type': 'distance', 'original_size': 246, 'resolution': 'high'}, 'time': {'data': [0, 1, 10, ... 1550, 1551], 'series_type': 'distance', 'original_size': 246, 'resolution': 'high'}} Previously, the response string included a section that was structured as follows (but with actual lat/lon pairs):'latlng': {'data': [[0.0, 0.0], [0.0, 0.0], [0.0, 0.0] … [0.0, 0.0], [0.0, 0.0]}... Is this a bug, did I miss an API change, or perhaps did I change something in my code without realizing it? Thank you in advance for any assistance. 

I've been using my individual Strava application for months, managing the API with the official Strava node in n8n. As of today, it still works normally.Will these new policies affect my ability to continue using n8n with Strava?              

Hi Strava team,App: "Principle Guy" (client ID 213702), category Mobile App, direct integration(Firebase Cloud Functions, EU). We have a fitness mobile app + webapp; athletesconnect via OAuth.My API settings currently show:- Developer tier: Standard- Athletes that can connect: 999Currently connected: ~148Use case: time-boxed corporate wellness activity challenges, read-only activitydata, ~150–300 athletes per campaign, a few campaigns per year. No intermediary.Three questions about the new Developer Program:1. My app shows a 999 athlete cap, but the new Standard tier mentions "up to 10   athletes." Is my 999 capacity grandfathered and will it stay, or be reduced to 10?2. To keep my current Standard access (and the 999 cap) past June 30, is a Strava   subscription sufficient? I have an active-developer 3-month free code…. does   redeeming it preserve the same access?3. For ~150–300 connected athletes per campaign, is Standard enough, or do I need   Extended Access? I'm well under the 10

Hello Strava Developer folks.  Thank you for the program update to the Developer API, good stuff and quite welcome.On the new subscription requirement for standard tier:  Your practice in the past has been to approve multiple Client IDs for different levels e.g. production, staging, testing, etc.  Each client ID requires a separate account, and these are all listed on the application.  In the new world will all levels require a subscription, or just the production level for an app?  Or perhaps you mean that once an app is approved for Extended Tier, then all associated Client IDs are upgraded and no longer require a subscription?Thanks for the clarification,Dave

Hi Strava Developer Team,I am building a personal automation workflow for my own account and need clarification on activity comment posting support.What I am trying to do:Post a comment on my own activity using:POST /api/v3/activities/{activity_id}/commentsCurrent behavior:OAuth token refresh succeeds. Access token is returned successfully. Granted scope includes activity:write (and activity:read). Reading activities and listing comments works. Posting comment consistently fails with:401 Authorization ErrorResponse body:{"message":"Authorization Error","errors":[]}Environment:Public Strava API app Single-player mode OAuth 2.0 with refresh token flow Request sent from both GitHub Actions runner and local machine Same result when trying to create commentsQuestions:Is POST activity comments currently supported for public API apps? If yes, are there additional requirements beyond activity:write? If no, is there an official alternative for automated responses (for example update activity de

Hello Strava Developer Community,I have a production Strava API application currently linked to the Strava account where it was originally created. (Personal account)Due to the recent Developer Program changes and the subscription requirement for Standard Tier developers, I would like to update the account login email to a corporate email address.I understand that migrating an API app from one Strava account to another may not be possible, so I’m considering simply changing the login email of the existing account.Before doing that, I would like to confirm whether this is safe.Specifically, would changing the login email affect any of the following?the API app itself; client_id / client_secret; existing OAuth access or refresh tokens; existing user authorizations; webhook subscriptions; developer tier status or future eligibility.The goal is to keep the same production app running without interruption, while managing the account from a corporate email going forward.Has anyone done this

Is there a function or any plands to develop that a segment could be created from location A to location B without a defined route one needs to follow? For example, running up a mountain as fast as possible, there might be many routes to explore, and the fastest  might actually differ between runners. 

Hello,I applied for Extended Access about two weeks ago but haven't received any response yet.My app details:Client ID: 166978 Category: DataImporterHow long does the Extended Access review usually take? Is there a way to check the status of my application?Thank you!

Hi Strava team,I'm posting here because I submitted both a user limit increase request and an email a few weeks ago and have not yet received any feedback.Our application, MindPriority, is a mental training platform built for endurance athletes (running, cycling, triathlon, HYROX, swimming, etc.). We recently integrated Strava because physical training data plays a key role in helping athletes understand the relationship between their training load and their mental preparation.Application details:Application Name: MindPriority Client ID: 245368If someone from the Strava team could review the application status or provide an update on the approval process, it would be greatly appreciated.Thank you for your time and for providing such a valuable platform for athletes and developers.Best regards,

Hi,We are developing an application to promote local challenges on Strava segments based on a community of runners in the different cities.We have already submit a request for review and provide answers to indicate how we are compliant with your terms of service. But since 1 month we have no feedback from Strava. Could you please check the status, we would like to release a beta version of our app and we already have many testers ready to participate.Best regards

Hi,According to the rate limit documentation I found here, the application’s current athlete capacity should be returned in the HTTP headers with every API request.I’ve made a few sample requests to the “/activities/{id}” endpoint, but I’m not seeing the athlete capacity listed in the response headers.  Everything else seems fine.  The response code is 200 and the data returned is as expected.  I’m receiving the other documented headers such as x-ratelimit-usage, x-ratelimit-limit, etc.Any ideas? Thank you,Gavin

Hello Strava Team,I am the developer of Strava API application Client ID 111268.Currently the application is limited to 1 connected athlete and I am receiving the following error when additional users attempt to authorize via OAuth:"403: Athlete limit exceeded"The application allows cyclists to connect their Strava accounts, synchronize activities and generate personalized training plans and performance analytics.Application details:Client ID: 111268Application Name: DDPEAKSWebsite: https://ddpeaks.com/Privacy Policy: https://ddpeaks.com/privacyThe application uses Strava OAuth and only accesses data explicitly authorized by each athlete.Could you please advise on the process to submit the application for production review and request an increase to the connected athlete limit?Thank you.

  But the email says: The full set of changes is below. Two things that aren’t changing: every Strava athlete can still access and download their data for free, at any time – and wearable and device integrations are not affected. Which is it????

I"m trying to conect Macative Pro to Strava, so I can use on my SmartWatch, but it had exceeded the athlete number.

Hi Strava community,I am trying to get some clarity on the review status of my Strava API application, Client ID: 222554.I have submitted the application twice and carefully followed the Developer Community guidelines, API Agreement, and the instructions in the Strava API FAQ and Developer Hub posts about the review and approval process. It has now been longer than the typical 7–10 business day review window that Strava mentions, and I still have not received any response or request for more information.In addition to the form submissions, I have also emailed developers@strava.com as recommended in the FAQs and developer program information, but I have not received any reply yet.Could someone from the Strava team please help with the following for Client ID 222554: Confirm whether my application is actually in the review queue Let me know if my app is not eligible for some specific reason Provide concrete feedback on what I would need to change or improve in order to be approved I

I have a few questions about how gear data flows from third-party bike computers (Garmin, Hammerhead Karoo, Wahoo, etc.) into the Strava API: 1. When a ride is uploaded from a Garmin or Wahoo device, does the device pass a gear/bike identifier to Strava, or does Strava rely solely on the athlete's default bike setting? 2. Is the gear_id on an activity ever populated automatically from the FIT file metadata (e.g. device sensor IDs), or is it always a manual selection by the athlete in the Strava app? 3. Are there any bike computers that currently pass gear assignment data through to the Strava API reliably? 4. Is there a recommended pattern for third-party apps like ours to correctly identify which bike was used for a given activity, particularly for athletes with multiple bikes? ThanksBen

Fail

Hi all (and Strava team),We've hit the 10 connected-athlete cap on our app, Linq iMessage (Strava Coach), and just submitted the Developer Program review form requesting a higher limit.The app is live and fully compliant: it's a text-message running assistant. Athletes connect with the standard "Connect with Strava" button, then text the agent to get their own runs, stats, heart rate, and PRs back. Specifics:- Read-only scopes (read, activity:read_all, profile:read_all)- "View on Strava" deep link on every activity shown- "Powered by Strava" attribution displayed- Tokens encrypted at rest; deauthorized + deleted the moment a user disconnects- Privacy policy: https://xy44jkfald.execute-api.us-east-1.amazonaws.com/privacyWe have real users at the cap and a growing waitlist. While the full review is in the queue, would it be possible to grant an interim increase (e.g. ~100 athletes) so we can keep onboarding? Happy to share screenshots of every data surface or hop on a call.Thanks!

I've already submitted the form 3 times for my app to be approved, but I'm not getting any response from Strava. On Monday, they increased my limit to 10 athletes, but I have over 500 athletes on my app, and we're growing gradually, but I can't sync them all, unfortunately.Does anyone know how to help?

At Strava, we’re constantly inspired by the passion and innovation within our developer community. Since we launched our new developer program, we’ve witnessed an overwhelming amount of interest and enthusiasm. It’s evident that many of you are keen to collaborate and continue contributing to the vibrant Strava ecosystem. Your invaluable feedback has allowed us to refine and improve the application process. As we iterate to ensure a streamlined submission journey, we recognize that additional time to submit for review would be appreciated by our community. In light of this, we’re excited to announce that we are extending the deadline for our Developer Program. This will provide everyone ample opportunity to be part of this exciting journey and ensure that all apps benefit. The new deadline will be March 4th, 2024. Thank you for your continued interest and feedback. Together, we look forward to building a richer and more dynamic Strava experience for our shared community. Sincerely,Stra

Hi All,With the changes happening next month, I have an application which has more than 10 users but less than 10,000, so I understand I will be classed as a Standard Tier dev. My application was previously approved. If I subscribe to Strava, does this automatically entitle me to 11–9,999 users, or do I need to go through the approval process again and potentially get rejected?Kind Regards,

Just wondering if other devs have got apps with > 10,000 users, but got allocated to the “Standard Tier”?Are we supposed to apply for Extended Access? What if we don’t, or get rejected? Do we get limited back to 9,999 users?

New API Policy §5.3 prohibits using Strava Data in AI, including data "derived from" Strava Data.My app calculates CTL, ATL, TSB from activity summaries via my own algorithms. Raw Strava fields (HR, power, pace) never reach any AI model - already removed.But when I send "CTL=62, compliance=80%" to an LLM for coaching advice - does that count as "derived from"?This likely affects every training/coaching app using the API. Clear on raw data. Unclear on calculated metrics.Artur (Client ID: 186368, Motus)

I have an app with the sole purpose of verifying if someone can run 5km under a specified time in order for them to join a club. It does this by scanning their Strava activity history and returning a yes or no answer. I don’t need to know anything beyond that so I don’t need them to be stored as a “connected athlete” going forward.   However, as I understand, by them just giving access for the app to scan their activity history this counts as an additional connected athlete right? And they remain as an additional connected athlete in the future (i.e. forever, unless they manually revoke access to your app). Is there a way around this? My initial thinking is webhook-based deauthorisation. After the worker gets the token and checks activities, this immediately call Strava’s deauthorise endpoint. This revokes the token and removes the app from the athlete’s authorised apps list on Strava’s side. In theory this should free the slot. Whether this actually frees the slot against the 10-athle

We have recently been upgraded to Standard Tier and are developing GOER, a consumer fitness platform integrating Strava activity data for gamified challenges and community engagement. We expect several hundred athletes shortly after launch and would like to understand the process, timeline and requirements for obtaining Extended Access Tier.