Welcome to Discussions! We're excited you're here. Find help, friendly discussions, and new member introductions in this space!
Recently active
Hi everyone,I’m developing RideTend, a bicycle maintenance app for logging rides, tracking service, and setting reminders. RideTend offers a monthly subscription for its own maintenance features, which use data entered directly in the app. We’re considering an optional Strava connection and a read-only activity view. Both would be available at no charge from RideTend, without requiring a RideTend subscription. Only the rider who authorizes the connection would see their activity data.I’d appreciate guidance on a design that fits the current Strava API Agreement and API Policy.Historical rides and automatic sync. Under §§5.5, 6.2 and 6.3, can we retrieve a limited set of older rides for the rider to view and use webhooks to reflect edits and deletions? Does the seven-day limit apply to how long we retain a fetched record, regardless of when the ride happened? Local storage and accumulated mileage. Our reading of §§5.5, 5.7 and 6.2 is that permanently saving activity records or IDs in on
Hi everyone, I run a small, free, non-commercial hobby app for a local running community. Each user's progress (a level and some points) is computed only from their own activities. I'd like to make sure we fully follow the 2026 API Agreement and Policy before resubmitting a capacity request. 1. Sharing with consent: Policy 2.3 says data can only be shown to the user it belongs to, while 5.13 mentions "prior express consent". Can we show a user's derived progress (no activity details, no maps, no Strava name) to other users of the app, if each user explicitly opts in (off by default) and can opt out at any time? 2. Retention: to recompute a user's progress, we keep a minimal summary of their activities (date, type, distance, elevation, time; no GPS or photos) while they use the app, and delete it when they deauthorize. Is that compatible with 6.2 and 6.4, or is a shorter limit expected? 3. Community channels: is it OK to post fully aggregated info (for example "6 users took part in this
It looks like a huge percentage of posts over the past few weeks and months on here are about Strava’s utter silence regarding the Connected Athlete / Rate Limit increases that are going unresolved, and the non-response from developers@strava.com . Perhaps it could be helpful if everyone in this same boat (I’ve been waiting 7 weeks, with no response) to all post here, and we can coordinate a list of all Client IDs and what they’re wanting (Athlete Limit increase, Daily Rate Limit Increase, etc), and provide that to Strava to streamline for their developers (best case), or take it somewhere more visible online to draw attention to this situation (worst case, if things are still up in the air for a while). It’s not the waiting that’s necessarily the issue (although we all want to be able to move forward with our applications) - it’s the complete silence, and not knowing whether it’ll be another week or 6 months before we can expect a response. Right now, this forum is just a flood of peo
Hello everyone,I'm hoping someone here can tell me what to expect, or whether someone from Strava can give a status.My situation - App: GlideHub, lap times for speed skating training, with optional upload of sessions to Strava - Client ID: 85786 - Platforms: web app (glidehub.nl, live since June 2026) and an iOS app (on the App Store since 29 October 2026) - Request: raise the athlete capacity from 10 to 1000 - Submitted: 8 October 2026, through the Developer Program review form. I received the automatic confirmation the same day ("It's under review, and there's nothing else you need to do for now"). - Follow-up: support ticket #19132 (23 October). The only reply was the automated one: capacity requests aren't reviewed by email. - Result so far: no decision, and no request for more information.Why it matters We have reached the cap of 10 connected athletes. New users, including active skaters who would use the integration every week (or a few times a week), can no longer connect their
I'm building a small app for group runs and club events. Before adding a Strava integration I'd like to check one use against the API Policy effective 1 June 2026.After a club 5K, a runner who has connected Strava sees their own activity from that evening in the app. If they tap "Submit as my event time", that time goes on the event's results board with their name and a link to the activity on Strava. Nothing is posted without that tap. We keep only the submitted time and the link, and remove the entry if the runner deletes it or disconnects Strava.The API data itself is shown only to the runner. What others see is the time the runner chose to submit. Is this allowed under 2.3 and 6.1 for a Standard Tier app with far fewer than 9,999 athletes If not, what would need to change?I also emailed developer support with the same question.
Hello,I'm developing AI Coach Personal MTB, a private training app for mountain bikers. Each athlete connects their own Strava account through the official OAuth flow. Right now only I am connected. My partner would be the second athlete, and Strava data is never shown to other users.The app sends a short summary of the athlete's own recent activities (date, sport type, distance, moving time and elevation gain) to an AI model, to generate a daily training suggestion and a weekly plan. The AI provider is Cloudflare Workers AI by default, and optionally Anthropic.Before I request production review, I'd like to confirm:Is this use permitted under the current API Agreement, given that the agreement prohibits using API data in AI applications, including prompts?If it is not permitted, what is the approved route for this kind of app (for example, written permission, or a different integration)?My developer dashboard offers "Upgrade subscription" to raise athlete capacity to 10. Does that upg
Hi, I submitted my app to the Strava API Program on October 9, 2026 and received the automated acknowledgment the same day (it mentioned a 7–10 business day review). It's now been about two weeks with no further response, so I wanted to ask about the status here.App name: TrailMetrics Client ID: 280243 App URL: https://trailmetrics.app/ Requested athlete limit: 5000 (currently limited to 10 and We’ve quite a few on the waiting list.) Scopes: read, activity:read, activity:writeI've also emailed developers@strava.com as a follow-up. Is there anything else I should do, or anyone who can check the review queue? Thanks!
Since I know this has been a frustrating place with the lack of timelines, I wanted to share that after about 6 weeks my application did get approval!No back and forth happened in my case. Got approved from 10 to 999 users. For those curious this is my Privacy Policy and ToS. https://skicap.app/privacyhttps://skicap.app/terms You will notice in there I explicitly state that I hold on to users GPS streams indefinitely until a user deletes it themselves, with the justification that I regularly analyze them as part of the key functionality of my app. I honestly did think this would get me a rejection, but I also noticed that getting a users activity via the stream does not count against my rate limit, so maybe that plays a part in it? Happy to answer questions, but honestly not sure how much more I can say then this lol.
Hi Strava team,I’m planning an app that creates personalized annual activity recap videos.Customers would authorize access through Strava OAuth. The app would fetch their selected year’s activity summaries and use fixed calculations and templates to render an MP4 on our servers. No activity data would enter an AI model.Customers would pay a one-time fee for the finished video. Only that customer could access it within the app, but they could download it and choose to share it publicly on social media.Could someone clarify:1. Is creating and charging for these videos permitted under the current API policy, including section 5.8?2. Can customers download and publicly share their own videos, given the rules limiting display to the authenticated user?3. Does this use require specific approval beyond the standard app review?We want to confirm the permitted scope before implementing the integration. Thank you.
Hi Strava team,I submitted the Developer Program form for kosu.co (Client ID [291409]) on [28/20/2026] and the confirmation email. We are at 10/10 connected athletes and requested a capacity of 999.kosu.co is a running race calendar and community. Connected athletes see, only for themselves, an estimated finish time and a readiness score for upcoming races based on their own last 12 weeks of runs.- Strava data is shown only to the athlete who owns it (never to other users or on public profiles)- No AI/ML use; data is never shared with third parties- We store only a 12-week run summary (no GPS tracks, heart rate or location) and delete it on disconnect or deauthorization (webhook)- Official "Connect with Strava" button and "Powered by Strava" logo are used- Webhooks instead of pollingCould you confirm the request is in the review queue, or let me know if anything is missing? Happy to provide more screenshots or details.Thank you!
Hi everyone,I submitted a Developer Program request for increased athlete capacity on October 24 for my app Routemaps (Client ID 88445). I haven't heard back yet, and email support says capacity requests aren't handled by email, so I'm posting here in case someone from the Strava API team can take a look.The app has reached the 10-athlete limit, so new users now get "403 – Connected athlete limit exceeded" and can't connect.About the app:- Routemaps (https://routemaps.pl) is a small Polish shop that turns an athlete's own activities into printed route posters.- We only read the activity the athlete picks (activity:read_all) and use it to draw the poster. Data is never shared with third parties or used for anything else.- We follow the Brand Guidelines: the official "Connect with Strava" button, "Powered by Strava" under the activity list and "View on Strava" links on activity cards.- Access is revoked automatically after 1 hour of inactivity, and users can disconnect at any time with o
Hello Strava Developer Support Team,We operate Phoenix Pack (https://phoenix-pack.uz), a community running club platform based in Tashkent, Uzbekistan.Our application has reached the hard capacity limit of 999 out of 999 athletes. All connected athletes are active runners participating in our weekly community runs and club challenges. Because our pool is completely full, new runners from our local community are currently blocked from connecting their accounts and joining club activities.We submitted our official Athlete Capacity and Rate Limit increase request through the developer form back on October 6, 2026 for Client ID: 173148 (almost a month ago), but have not received an update or status confirmation yet.Could someone from the API / Developer Review team please look into our application in the review queue? Please let us know if any further verification or details are needed from our side.Thank you for your time and assistance!Best regards,AndreyPhoenix Pack TeamClient ID: 17314
Hello Strava Developer team,We run Ridge (https://ridgetrail.app), an iPhone and Apple Watch app for hiking and trail running, live on the App Store since August 2026. Strava is optional: athletes can import an activity as a route and send recorded activities to Strava.Our app has been at its 10/10 athlete capacity for over a month. We submitted the official capacity increase form on September 30, 2026 and haven't heard back yet. Real users are now hitting the limit: one wrote to our support today after getting an error on the authorization page.Our integration follows the guidelines your team highlights:- Webhook subscription in place (subscription 374767); deauthorization events are handled- Revocation on disconnect, and a 401 clears the local connection and the cached data- No background polling: every API call follows an action by the athlete- No activity data stored on our servers; our backend only brokers OAuth tokens, and the client secret never ships in the app- Official "Conne
Hi Strava team,I submitted an athlete capacity increase request on October 15 and haven't received any response yet, so I'm following up here.App details:• App name: iRunning• Website: https://irunning.app• Client ID: 247791• Current limit: 10 connected athletes• Date submitted: October 15, 2026iRunning is a running app for iPhone and Apple Watch. The Strava integration lets our users upload the runs they record in iRunning to their own Strava account. Each athlete only authorizes access to their own data, and we only write the activities they recorded themselves.We're at the 10-athlete cap, so new users who try to connect Strava are blocked. Strava sync is the single most requested feature from our users: every day new users write to us asking when they'll be able to connect their account, and right now all we can tell them is that we're waiting on Strava. The request to raise the limit has been sitting without a reply for over three weeks.Could someone confirm the request was receive
Hello Strava team,RidePeak (https://ridepeak.app) is a cycling training planner, Standard Tier, currently at 10 athletes and preparing a capacity request. Each athlete sees only their own data; no sharing, no leaderboards, no AI.To plan training we need a daily training-load value (TSS) per athlete over roughly 6–12 weeks (chronic/acute training load). Before we redesign our data model we would like to confirm which of these patterns is compliant:A) Delete all Strava activity records within 7 days and retain only a daily load number (e.g. "2026-10-14: 87 TSS") for that athlete, deleted on deauthorization within 48 hours.B) Store nothing beyond 7 days; on each use, re-fetch the athlete's activity list (last ~90 days) from the API, compute the load in memory and discard it.C) Neither – Strava data may only be used for the last 7 days.Which of A, B or C is permitted under Sections 6.2, 6.4 and 7.4? If B, does it count against normal rate limits only?Thank you,Wolfgang Marx – RidePeak
Hello Strava Developer Community,App Name: Da HaloClient ID: 191535We submitted a request to increase our connected-athlete limit approximately two months ago, but we have not received any response or update regarding our application.We have now reached the current maximum connected-athlete limit, which means new users are unable to connect their Strava accounts through our app. This is directly affecting our users' experience.We understand that requests may take time to review, but after waiting for two months without any communication, we would greatly appreciate any update on the status of our application or guidance on how to move forward.Has anyone experienced a similar situation or found an effective way to get an update on a pending request?Thank you for your time and help.
Our application has reached the 9,999 connected-athlete cap, and new users can no longer authorize the app. This is currently blocking all new sign-ups in production.DetailsApp name: Avionx Ride Client ID: 153306 Owner / contact email: develop@avinox-ebike.comWhat we've already doneSubmitted the athlete-limit increase request via developers@strava.com on 2026-08-17 Completed the API agreement / brand guideline requirements and confirmed our app is compliant No reply received in 10 days, and no update on the request statusWhat we're asking forConfirmation that our upgrade request was received and is in the queue Guidance on the expected review timeline, or any missing information we should provide If possible, an interim limit increase so existing production traffic isn't blockedHappy to share additional details (usage patterns, rate-limit stats, screenshots, or a Strava-facing walkthrough of the app) via a private channel. Any pointer to the right process or contact would be greatly ap
I run a small coaching app (DM Training) where clients connect their own Strava account via OAuth. We’d show their activities to them and to the coach they hired, who uses them to adjust training. Nobody else sees the data, and it’s never used for AI/ML or shared.Since the Nov 2024 agreement update, is coach visibility allowed, or must data be shown only to the athlete? Has anyone with a coaching platform passed the capacity review with this use case? Any official Strava answer would be very welcome.
I'm building Aevo, an endurance coaching app. An athlete connects Strava, and we use their activity data to coach that same athlete. Part of the coaching is generated with an LLM (OpenAI API), used for inference only.I want to stay on the right side of the API Agreement, and I could not resolve this from the Agreement text or existing threads.The Agreement is clear on two points: data obtained through the API may not be used to train AI or ML models, and a user's Strava data may only be displayed or disclosed to that same user. What it does not address is inference.My question: is AI inference on an athlete's own data, used solely to generate guidance for that same athlete, permitted? To be specific about my setup:No model training, fine-tuning, or improvement on Strava data, ever. A user's data is only ever shown to that user, never to others, never aggregated. Zero data retention can be enabled on the OpenAI account so inputs are not stored. Only derived metrics (pace, distance, HR s
Hi,I'm the developer of Amberday, an iOS app (Client ID: 293429) that gives athletes a daily training verdict (maintain, lighten, or rest) based on their recent training load and, optionally, Apple Health recovery data. Training history, load and the verdict itself are computed from Apple Health workouts, on the athlete's iPhone, and shown only to that athlete. Strava is used for the last 7 days only: activity names and routes in the app's calendar, and the optional sharing described below. All Strava data is removed from the device after 7 days, per Section 6.2. I'd like to make sure the app complies with the API Agreement and API Policy (effective June 1, 2026) before requesting a capacity increase. Two questions:1. Adding a short block to the athlete's own activity description (activity:write)The app has an opt-in setting, off by default. When the athlete turns it on, the app requests the activity:write scope and appends a short block of four lines to the description of that athlet
Hi Strava Developer Team,I am following up on a request to raise the athlete capacity for my application (Client ID: 231801). I have not received a reply or any news on the review.Athletes who try to connect now see this page on strava.com:Error 403: Connected athlete limit exceeded. "This application has exceeded its connected athlete limit."The app is Kulsans (https://www.kulsans.com) — a team platform for running, trail, and gym coaches, built by Cenit Solutions. The coach plans the week. Each athlete connects their own Strava account so a completed activity can close the planned session, with distance and time. Coaches see that data only when the athlete shares it with that team. The connection is read-only (read, activity:read_all). We do not post to Strava, and we do not republish an athlete’s feed.The default cap is already full, so the next athlete cannot authorize the app. I need the cap raised so every athlete on a team can connect.Can you tell me the status of this request,
Hi Strava team,every athlete knows the moment: the last kilometre, the noise, the clock above the finish line. A few days later the medal is in a drawer and the activity is somewhere deep in the feed. Zielglück exists to keep that moment – we turn one of the athlete's own activities into a printed poster for their wall: the route line, the distance, the time, the date.On October 28, 2026 we submitted an athlete capacity request for our app (Client ID 291382) and have only received the automatic confirmation so far. We know reviews take time, so here is everything in one place to make it as easy as possible.Why Strava matters to usMost people design their poster on their phone, often right after the race – and on a phone, exporting a GPX file is close to impossible. "Connect with Strava" is the one simple way for them to bring their own run, ride or hike onto the poster. We are a complement to Strava, never a replacement: no feed, no leaderboards, no segments, no training analysis, no s
Hi everyone,I'm developing a custom indoor running app that connects to treadmills via Bluetooth FTMS.The app records speed, distance, heart rate, incline, and calculates elevation gain based on the treadmill's actual incline.The elevation gain is correctly calculated in the app and stored in the generated FIT file. However, when I upload the activity to Strava, the elevation gain always shows 0 m.Here's an example from a recent workout: Distance: 3.27 km Duration: 18:57 Calculated elevation gain: approximately 283 m Elevation gain displayed in Strava: 0 m Activity type: Run (not Treadmill) I'm currently investigating whether the FIT file needs additional altitude-related fields or whether Strava ignores elevation data for indoor running activities.My questions are: Does Strava require specific FIT fields (altitude, enhanced_altitude, total_ascent) to display elevation gain? Does Strava ignore elevation data from indoor running activities? Would uploading the activity as Vi
Hi! My API app (Client ID 77411) shows "-1 requests every 15 minutes, -1 daily" for both overall and read limits. Every request returns HTTP 429 with X-RateLimit-Limit: -1,-1, even with minimal usage (17 requests). I have an active Strava subscription, the app is for personal use (reading my own activities), and I can't delete it to create a new one. I already contacted developer support (ticket #19425). Could someone from the Strava team restore standard limits for this app? Thanks!
Hello Strava Team,I would like to request an athlete capacity increase to 30 authorized athletes for [Training] (Client ID: [165886).I previously submitted a review request but have not received a response. I no longer have the exact submission date or a reference number, so I am posting here to request guidance on the appropriate next steps.What the application doesThis is a small, personally maintained, non-commercial website for approximately 30 members of a cycling group.Its purpose is to summarize participants’ weekly virtual cycling activity. Each member creates a website account and individually connects their own Strava account through OAuth.The application calculates weekly totals using the moving_time of eligible VirtualRide activities, with weeks defined in the Asia/Shanghai time zone.How we use the Strava APIScopes requested: read,activity:read. The application does not request activity-write access. Activity retrieval: Read the authorized athlete’s activity list and retrie
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.