Curious about our API? Connect with our developers to share ideas, knowledge, and feedback
Recently active
I would like to suggest an improvement to Live Segments for Premium subscribers.Currently, Live Segments only allow comparison against a Personal Record (PR) and the segment KOM/QOM/CR. While this is useful, it would be much more valuable if users could choose the reference they want to compete against during the segment.Suggested options could include: Personal Record (current option) Last attempt Best effort within a selected time period (e.g. last 90 days or current year) A custom target time entered by the user A selected friend or follower A previous activity chosen by the user For many athletes, especially those training consistently, comparing against a recent performance or a specific target time is more motivating and relevant than comparing against an old PR or an unattainable KOM.This feature would make Live Segments a much more powerful training tool and would add significant value for Premium subscribers, particularly for those using the Strava mobile app.Thank y
Hi Strava API support team and the community, Let me write a few lines to have the contextI initially submitted to the API Development program in May, 10, and never got back any response until Jun, 01, when the API program changed On Jun, 07, I submitted a support ticket to developers@strava.com, and the support team instructed me to submit a new form for review since my previous submission was closed due to changes in the API policy. I’m ok with that and submitted again. Today, Jun 11, I received this email and don’t know what I have to do next, since my app already reached the maximum athlete capacity, already implemented webhooks to receive the workout data, and manages stale and deauthorized athletes. Also, I’m sure that my app complies with the new API Agreement and API Policy Here is the information about my appApp name: Pace ID Primary Client ID: 233610 Additional development app Client ID: 238433 Production domain: https://paceid.netPlease let me know the next action I should
Hi everyone,Posting here for visibility on a Developer Program form submission, as suggested by the support auto-response.CONTEXTI just submitted the Developer Program form on June 9, 2026 to request an athlete-capacity increase for my application Esprit Trail (Client ID 232321), currently in Single Player Mode. Form confirmation acknowledged the submission ("Thank you for submitting your application for review — Strava API Team").WHAT THE APP DOESEsprit Trail is a companion app for trail runners: AI-assisted training plans, a curated trail-race calendar, training-spots discovery and a community space. Connecting Strava is the recommended onboarding path so the athlete's past and new activities populate their stats, training plan and history.- Web: https://esprit-trail.vercel.app- Distribution: PWA on the web + Android app published on Google Play (TWA wrapper)API USAGE SUMMARY- OAuth 2.0 authorization code flow with refresh-token handling- Scopes: activity:read_all, profile:read_all (
Hi everyone,I'm the developer of Wattvana (wattvana.app), an AI-powered cycling training app built on the Strava API. We're in open beta and currently hitting the 10 athlete limit.Use case: Read-only access to athlete activities and streams to calculate training load metrics (CTL/ATL/TSB), power curves, and generate adaptive weekly training plans.Client ID: 247593Could anyone guide me on how to request an athlete capacity increase? Thank you.
Hello Strava Developer Support,I am the developer of a Strava API application and I am receiving the following error when a second athlete tries to connect:Error 403: Limit of connected athletes exceeded.App name: O Acre Existe e PedalaClient ID: 256754The app is intended for internal cycling community management purposes only. Members of our cycling community voluntarily authorize access to their own Strava activities so we can import basic activity data into a private Google Sheets leaderboard.The app does not collect passwords and does not scrape public profiles. Each athlete must authorize access through Strava OAuth.We would like to request an increase in the connected athlete limit to allow multiple cyclists from our community to connect.Requested initial capacity: 100 connected athletes.Thank you.
Hi all,I submitted the Developer Program form on April 12, 2026 to move my app out of Single Player Mode, and emailed developers@strava.com as a follow-up about a week ago. No reply on either so far.Reading other threads I see this is fairly common, so two questions for the community:1. What's a realistic current timeline? Recent posts mention anything from 1 week to several months — has anyone been approved recently (April–May 2026)?2. Anything that helped speed it up? Specific format for the follow-up email, screenshots to attach, contacts that worked?For reference, my app:- Name: ReadyRun (AI running coach, Android)- Client ID: 216890- Site:https://readyrun.run- Webhook already configured and validated, OAuth flow tested end-to-end- Read-only scope, no write-backIf any Strava staff happens to see this and can check the status, I'd really appreciate it. Otherwise, any tips from devs who've been through this recently would be gold.Thanks!Sergio
I have developped an application that sends heart rate from a Wear OS watch to Garmin Edge bike computers. Heart rate is saved in a developer field that should override heart rate native values. I do the same for power (in a developer field inside the fit file). Power is displayed on Strava but not heart rate. It would be great if Strava displays heart rate values from developer fields with nativenum = 3 when heart rate is not already present in the .fit file.This way people will be able to use their Wear OS smartwatch as a HRM together with their Garmin GPS and get heart rate on Strava.Thanks for your consideration
Hi all,With the updated API Policy (June 1, 2026), Section 5.3 prohibits using Strava Data "in connection with the development, training, evaluation, or operation of any AI Application," explicitly including "ingestion into a context window or working memory."I'm trying to understand how broadly this applies. My app (The Personal Shift, Client ID 191370) does the following:Fetches athlete A's own activity data via the APIPasses it transiently to Google Gemini (inference mode only — no training, no fine-tuning, no embeddings, no persistent index)Returns a personalized coaching note displayed exclusively to athlete AThe Strava data is not retained in the AI layer beyond the 7-day cacheThis is strictly one-to-one: athlete A's data is only ever used to generate output for athlete A. No aggregation, no third-party data sharing, no model training of any kind.My question: Does Section 5.3 prohibit this type of use, or is it primarily aimed at bulk data ingestion, model training, and aggregati
Hello everyone,I am looking for some guidance regarding the Strava Developer Program review process.I submitted a request on April 29 to increase the athlete capacity limit for my application.Ticket number: 14925Client ID: 221219At the time, I was informed that the review process would take approximately 7 to 10 business days. However, this timeframe has already passed, and I have not yet received a clear status update regarding the approval.My web application is already fully developed and ready to be launched. At this point, the launch depends exclusively on the approval of the athlete capacity increase, since the current limit prevents additional athletes from connecting through the Strava API.I have already contacted developers@strava.com, but I would like to know if there is any recommended way to follow up, escalate the request, or confirm whether the application is still under review.Any guidance from the Strava team or from other developers who have gone through this process wo
Hi Strava Developer Support Team,I recently submitted a request to increase the API rate limit (Athlete Capacity) for my application.My app, "VietinBank Bắc Hà Nội - Happy run 2026", is strictly an internal application built to host a short-term, non-commercial running event celebrating our 75th company anniversary. We are expecting exactly 400 internal employees to participate.Due to a critical timeline, our official event launch is scheduled for tomorrow, June 6th. We are currently locked at the standard 10-user capacity, which completely blocks our employees from connecting their Strava accounts to our internal leaderboard.We fully comply with Strava's API guidelines and branding. I have attached screenshots/screencasts of the user flow and the "Connect with Strava" button for your quick review.App Details: Client ID: 255063 Requested Capacity: Extended Access (for ~400 users) Purpose: Internal leaderboard for a private company run. Could you please help us expedite the review p
Right now I am on Standard Tier and already 10 athletes limit reached. I have requested for more users but I don’t think the support team have time and they will do it.I am ready to purchase the API and want to upgrade to Extended Access Tier if possible and available.How can I purchase it?Below are the important links of the application I have developedGoogle Play Store - https://play.google.com/store/apps/details?id=com.suratriders.surat_riders_cyclingApple App Store - https://apps.apple.com/us/app/surat-riders/id6771241915Web App - https://surat-riders.web.app/
Hi Strava Team,We submitted a rate limit increase request for our private app (Client ID: 255520).To expedite the review, we have already updated our website to fully comply with the Strava Design Guidelines (using official "Powered by Strava" assets).App Purpose: Strictly non-commercial, internal fitness challenge for our employees. Completely closed to the public. Request: Increase the athlete connection limit to 100 so our staff can participate.Could a team member please help flag our request for an early review?Thank you for your support!
Hello Strava Team,I hope you are doing well.I am writing to kindly request an increase in the athlete capacity limit for our application (Client ID: 237316) from 1 athlete to 999 athletes.Our application is already in production and available at:https://www.vasudevcyclingclub.comWe submitted the API review form on May 11, 2026, and we are still awaiting a response regarding the review status. The current athlete limit is the only remaining blocker preventing us from onboarding our cycling community and fully launching the platform.About Our ApplicationVasudev Cycling Club is a community-driven platform designed to motivate cyclists to ride consistently and improve their overall health and fitness.With the athlete's consent through Strava OAuth, our platform:Retrieves athlete riding activities from Strava.Calculates cycling statistics and performance metrics.Displays community leaderboards on our website.Encourages healthy competition among cyclists.Motivates riders to stay active and m
Recently our users sync activity to strava, the api status code is 201, but they can’t find their activity in strava app. Our oauth2 app client id is 15011, the response is like:{ "activity_id": null, "error": null, "external_id": "e5e62cba-c9b2-4f21-912f-588e54ed97fb.fit", "athelete_id": 134004803, "upload_id": 17517421023, "id_str": "17517421023", "status": "Your activity is still being processed."}My problem is why our user can’t see the uploaded activity. Another problem, our App has exceeded the limit of connected athletes.Given the gradual increase in our app's user base and their strong affinity for Strava, we require additional quotas for uploading activity data to Strava.Could you tell us how to request a quota increase? Thank you.
I am unable to retrieve my activities via my React application, despite using this how-to site for reference and largely copying the code over: https://javascript.plainenglish.io/strava-api-react-app-326e63527e2c. Is this not a valid request link: https://www.strava.com/api/v3/athlete/activities?access_token=<access_token_here>? Of course, that <access_token_here> part is where my current access token would be, which gets refreshed with the way I've set up my React App.js file. For extra context, I am receiving a 401 request error upon the request being made in React: The underlying error appears to be the following: Not sure how to interpret this result. I'd appreciate any help/insight into this for those of you who are aware of a fix/solution and/or have gone through this problem already.
Hello everyone, I am running a strictly personal, non-commercial application designed to host a yearly challenge among a closed group of friends (up to 150 users maximum). I want to ensure we are 100% compliant with the recent API updates.Since the automated email support referred me here for API policy questions, could someone from the Strava team please clarify our case?Can you confirm whether our non-commercial app for up to 150 users can remain unchanged under the updated API terms if it currently includes a leaderboard that shows participant comparisons? If not, can you confirm whether it would be compliant to remove leaderboards and instead show each user only their own totals plus one anonymized community progress total that aggregates all users’ distance without revealing any individual athlete’s identity, activity, or contribution?We want to do this right and stay fully compliant. Any official guidance from the Strava API team would be highly appreciated!Best regards, Filip
I have an app that uses the Strava API. It works just fine. I’m now building a second app, unrelated to the first, and also want to use the Strava API. Do I need to create a separate Strava account in order to register the new app for API usage? If I’m able to have multiple apps on the same Strava account, how do I add separate callback urls -- does it accept comma-separated values?I saw the API is moving to subscription-only; that would be problematic as I’d have to have a separate Strava subscription for each app using the Strava API.
Hi,Since I upgraded (today) my app to the new Standard Tier, every API call returns HTTP 500 with body {"message":"error"} across all endpoints, all athletes, and even the "Your Access Token" from my developer dashboard.Reproduced with curl directly (no intermediary code):bashcurl -i https://www.strava.com/api/v3/athlete \ -H "Authorization: Bearer <dashboard token>" HTTP/2 500{"message":"error"}x-envoy-upstream-service-time: 42x-request-id: e180229a-1c45-4773-9f0d-4ad558b0cacdEndpoints tested: /athlete, /athlete/routes, /athlete/activities. Same result on all of them.The OAuth flow completes fine, tokens are issued with sensible expires_at, so it looks like the backend is rejecting every call from this client_id post-upgrade.App: MoguWind client_id: 236823Has anyone else hit this after the tier migration today? Is there a propagation delay, or an extra step I might be missing, terms acceptance, billing, something else?Thanks, Javi
I would like to request API support for the newer activity tags, especially tags such as “With Kid”, “With Pet”, “Commute”, etc.Currently, some activity context is exposed through the API. For example, the activity response includes fields such as:"commute": falseHowever, other activity tags that are available in the Strava UI do not appear to be exposed in either:- GET /athlete/activities- GET /activities/{id}For example, I added the “With Kid” activity tag to a run in the Strava UI. When retrieving the activity through the API, I can see fields such as:"commute": false,But I do not see any field that indicates the activity has the “With Kid” tag. There is no obvious field such as:"tags": [...]or:"activity_tags": [...]or:"with_kid": true
Hi Strava team,I'm requesting increased athlete access for StriveFlow StriveFlow is a GPS fitness tracking app for Android launching on Google Play. Users can track cycling, running, hiking and walking workouts and upload completed activities to their Strava account. We only write activities — we don't read other athletes' data.We are about to launch publicly and the 10 athlete limit will prevent users from connecting. Is there a self-upgrade option or can you increase our athlete limit?
Hi Strava community,I applied for an API rate increase for my application in May with no response. With the new API guidelines announced June 1, am I expected to re-submit an application or am I still in the queue? In addition, where can I find the link to the new API rate increase application? Any help would be greatly appreciated, thank you.
Hello Strava Support Team, I hope you are doing well. I would like to request a refund for a recent subscription purchase made on my account. Below are the details: Subscription: Strava (1-Year Plan)Amount: ₱1,500.00Date & Time: March 17, 2026, 8:38 PM Payment Method: Maya (via Google Play)I did not intend to purchase this subscription, and it was made accidentally. I have already canceled the subscription shortly after noticing the charge, and I have not made use of the premium features. For your reference, I have attached a screenshot of the transaction and subscription details. I kindly ask for your consideration in processing a refund for this charge. I would really appreciate your help with this matter.Thank you for your time and understanding.Sincerely, Andrei San Andres
Hi,I submitted a request to increase my athlete capacity (Client ID: 228959) on May 7. The documented review time is 7–10 business days, but it's been over a month with no response — the June 1 update auto-bumped me to 10, but my request is still pending with no answer.How can I check the status of this request? We already use webhooks and respect rate limits. Thanks!
Hi Strava Developer Support Team,I am writing to request an increase in the connected athlete limit for my application.App Details: App Name: Ba Thôn Runners Club Client ID: 190564 Use Case: I have developed this application to help manage running events, challenges, and track results for our local running club. It simplifies our coordination and motivates our members to run more.We have currently reached the default limit for connected athletes, and I would like to request a limit increase to 50 athletes so that all our club members can participate in our upcoming running events.Our application complies with Strava's API Agreement, including the proper display of the "Powered by Strava" logo.Please let me know if you need any further information from my side.Thank you,
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.