Recently active topics

I appreciate that you tested this the Strava MCP with Claude so I imagine it works, but they aren’t the only agent out there. I’m getting an immediate HTTP 403 with Copilot CLI, and when having it introspect why, it reports:Root cause: it’s not failing because your  strava-mcp  entry is missing or malformed; Copilot is rejecting Strava’s OAuth metadata as invalid.Your config is a normal remote MCP entry in  ~/.copilot/mcp-config.json :"strava-mcp": {  "type": "http",  "url": "https://mcp.strava.com/mcp"}But the Copilot log shows the auth flow dies here: OAuth authentication failed for strava-mcp: MCPOAuthError: Incompatible authorization server: authorization server advertised an issuer that does not match the URL its metadata was discovered from (RFC 8414 §3.3); refusing to connect What’s happening is:1.  strava-mcp  challenges the client with an OAuth protected-resource URL on  www.strava.com .2. That metadata points to  https://www.strava.com/mcp-issuer  as the authorization server.

Hi everyone,I'm about to start building a fitness application on Strava API v3 under the Standard Tier developer program. My app lets individual users authenticate via OAuth 2.0 and sync their personal activity records into my app's database.Before I start development, I wanted to confirm that the following endpoints are fully available (read + write where applicable) under Standard Tier:Activities: GET /athlete/activities, GET /activities/{id}, POST /activities Streams: GET /activities/{id}/streams (GPS, heart rate, power) Webhooks: POST /push_subscriptions (for real-time sync instead of polling) Athlete Data: GET /athlete, GET /athletes/{id}/statsI've already checked the changelog and understand that the Club endpoints (Activities/Members/Admins) were removed and GET /segments/explore now requires Extended Access Tier — so I'm not asking about those.Two questions for the community:Can anyone confirm these four groups are unaffected by the recent Standard Tier changes and still work a

I completed the request from a week ago after following all the instructions very specifically (making sure all 10 athlete connections were already used, full documentation and screenshots of how the athlete connections are used etc.Our application is in a closed beta process with coaches and not being able to support the majority of them (it’s a solution for team sport coaches) and every team has 20 - 40 athletes so the 10 connections were used up rapidly and now all our other teams can’t complete the full test experience.Is there any way to make this visible and even just get a semi accurate timeline that we can provide back to the coaching staff of when this is likely to be possible?Details of the application are at https://www.conditiond.app

Hello Strava Developer team,I am developing CycloCoach AI, a personal cycling training and analysis application currently preparing for a very small private beta.The application would allow an athlete to connect their own Strava account through OAuth and retrieve their own activities in order to: display their training history; calculate personal metrics such as training load, progression, records and consistency; compare planned sessions with completed activities; provide personalized explanations and training recommendations; adapt the athlete’s future training plan based only on their own activity data. The data would remain private to the connected athlete. It would not be sold, publicly shared, used for advertising, or made visible to other users.We would also not use Strava data to train a general-purpose AI or machine-learning model.Before opening the private beta, we would like clarification on the following points: Is the use of Strava API activity data for individual

Hi all,I'm looking for advice from developers who have been through the athlete capacity increase process.I run Fencingmetrics, a free web app for fencing clubs in France (results and rankings, training load, video analysis). Strava is one of the sources for training load: a fencer connects their account, and their activities feed a CTL / ATL / TSB model shown on their own dashboard.The app is still on the default cap of one connected athlete. I submitted a capacity increase request on 31 August (client ID 257652) and haven't heard anything since — no acknowledgement, no refusal. Meanwhile, fencers who want to connect Strava can't, and I'm stuck on this part of the project.Usage is light: one sync per athlete when they open their dashboard, at most every 12 hours, 30-day window, no background polling. "Powered by Strava" branding is in place, and the support page covers disconnection and data deletion.A few questions for those who've been here:What is a realistic response time these da

Hey everyone,I'm a developer planning to build a cycling and running training app integrated with the Strava API, and before I start I'm trying to get clarity on the AI restrictions introduced in the November 2024 API Agreement update.I understand that using Strava data to train or fine-tune AI models is clearly prohibited. What I'm less sure about is whether the restriction also covers inference-only use cases, specifically:1. Sending a user's own Strava data as context in a single prompt to an external LLM API (Claude, GPT-4, Gemini etc.) to generate a personalized training plan or coaching feedback — no model training, data used only for that one request, result shown only to that user2. Running a self-hosted local model on my own infrastructure (e.g. LLaMA, Mistral), where Strava data never leaves my server and zero training on Strava data occursHas anyone dealt with this and got a clear answer from Strava — either via the review process or by emailing developers@strava.com?I've al

Hello Strava Developer Support,I’m developing PerformanceLAB, an endurance training and performance platform using the Strava API.Client ID: 190585Developer level: StandardAthlete capacity: 10Connected athletes: 1We are consistently receiving HTTP 429 Too Many Requests when calling:GET /api/v3/athlete/activitiesWe have instrumented the API response and captured the following rate-limit headers from a real request:X-RateLimit-Limit: -1,-1X-RateLimit-Usage: 3,9X-ReadRateLimit-Limit: -1,-1X-ReadRateLimit-Usage: 3,9Retry-After: not presentThe application dashboard also displays:Overall Rate Limits: -1 requests every 15 minutes, -1 dailyRead Rate Limits: -1 requests every 15 minutes, -1 dailyThe API usage shown in the dashboard is very low, yet /athlete/activities consistently returns HTTP 429.According to the current Strava API documentation, expanded access with an athlete capacity of 10 should provide read limits of 200 requests / 15 min and 2,000 / day, and overall limits of 400 request

I’ve tried several times in several different browsers to open the link from Question #2 in the Strava API FAQ.The link to the form is http://share.hsforms.com/1VXSwPUYqSH6IxK0y51FjHwcnkd8, but clicking it gets the same response from multiple browsers:Is it no longer used? Is something in its place? Or is this an issue on the Rook side of things?

Hello Strava Developer Team,We have submitted KASATI Running for Developer Program review and would greatly appreciate your assistance with an expedited review due to an upcoming internal employee wellness program.Application: KASATI RunningCompany: KASATIClient ID: 276655Current Athlete Capacity: 10Current Connected Athletes: 10Requested / Intended Users: approximately 400 employeesProgram Start Date: September 15, 2026Company Anniversary: October 10, 2026 – KASATI’s 41st AnniversaryWebsite: https://erp.kasati.com.vn/running/Privacy Policy: https://erp.kasati.com.vn/running/privacy.phpSupport: https://erp.kasati.com.vn/running/contact.phpKASATI Running is a private internal corporate wellness application for KASATI employees in Vietnam. Employees voluntarily connect their individual Strava accounts through OAuth 2.0 to access their authorized activity information.We have reached our current athlete capacity of 10, and approximately 400 employees are expected to participate in our upco

Hi API Support Team,I am checking on the status of a Rate Limit Increase request submitted via the official form on August 16st for our non-commercial community application "Ausprá" (Client ID: 262234)App Overview: Use Case: Non-commercial community cycling challenge leaderboard aggregation Authentication: OAuth 2.0 (activity:read / activity:read_all) Status: Currently operating with 10 authenticated test athletes on the Standard tier. Target: Scaling to 150 active participants for our upcoming challenge Architecture: Scheduled limited punctual fetch to avoid real-time API stress Could an admin or team member please check if our submission is queued for review?Thank you for your assistance!

Hi, I am building an app with that uses Strava authentication and have a “Log in with strava” button on the app. I’ll need to have that functionality reviewed for the App Store, but I’m not sure how to do that. I had assumed they could use my test account for review so I created one but was immediately routed to MFA during sign up. Is there any way to use a password login anymore for a use case like this? 

https://www.strava.com/api/v3/athlete/activities?before=1789454741&after=1773557141&page=1&per_page=30{"error_type":"0","url":"https:\/\/www.strava.com\/api\/v3\/athlete\/activities?before=1789454741&after=1773557141&page=1&per_page=30","curl_result":"{\"message\":\"Forbidden\",\"errors\":[{\"resource\":\"Application\",\"field\":\"Status\",\"code\":\"Inactive\"}]}"}Your subscription will be changed to an annual fee of $1,490.00 on October 4, 2026.Is the API inactive due to the current free trial period?

Hello Strava Developer Community, I need help registering an API application. I am logged into an active Strava subscriber account, but https://www.strava.com/settings/api does not display the “My API Application” page or the app-registration form. It only shows general account settings. I contacted developer support and received automated ticket #18157, which directed me to this forum. Planned application:- Name: RunCoach Pro- Website: https://run.traslospasosdedavid.org/- Category: Training- OAuth callback domain: run.traslospasosdedavid.org- Use case: athletes voluntarily connect through OAuth so the platform can import their own activity summaries for personalized running coaching. The integration is read-only and will not store GPS coordinates or polylines. I need access to the API dashboard to register the application and obtain the client ID and client secret. Could someone confirm the current eligibility requirements and the correct troubleshooting or support path when the API

Hello,I'm developing an application (still in testing, not yet published) integrated with the Strava API, and I'd like to better understand a behavior that doesn't match the documentation.Application details:- Client ID: 208201- Category: Other- Developer level: Standard level- Token scope: readThe issue:I received a 429 error (Rate Limit Exceeded) when calling the activities endpoint (Get_Activities), even with very low usage volume. Checking the "API Usage" panel on my application's page, the total for the day was only 20 general requests and 20 read requests, and the most recent 15-minute block showed only 5 requests — well below the documented default limits (200/15min and 2,000/day for overall; 100/15min and 1,000/day for read).I also noticed that, on the "My API Application" page, the "Overall Rate Limits" and "Read Rate Limits" fields show as "-1 requests every 15 minutes, -1 daily". I'd like to confirm whether this value is just a display placeholder (with the default limits st

Hola, solo quería comentarles que solicité recientemente una extensión de conexiones para mí app, de 10 a 999 y la aprobaron exitosamente en 3 días. Escribo esto porque leí varios mensajes aquí sobre demoras o negativas a estas solicitudes, recomendando que revisen detalladamente los términos y condiciones Strava, tanto de uso de marca como de conexiones, para evitar estás demoras y que sus solicitudes se aprueben rápidamente. Saludos 

Hello Strava Developer Community and Strava API Team,I’m reaching out on behalf of KASATI regarding our internal application, KASATI Running.We previously contacted Strava Developer Support by email regarding an athlete capacity increase. We received an automated response advising us that athlete capacity and rate-limit increase requests are not reviewed by email and recommending that we post in the Developer Community Hub.We would therefore appreciate guidance from the Strava team on the correct next step for our application review.Application overviewApplication: KASATI RunningOrganization: KASATIUse case: Private internal employee wellness and running programCurrent athlete capacity: 10Current connected athletes: 10/10Requested capacity: Approximately 400 athletes/employeesProgram start date: September 15, 2026KASATI 41st Anniversary: October 10, 2026KASATI Running is a private internal corporate wellness application developed for KASATI employees in Vietnam.Employees voluntarily co

Strava API Developers,I was checking in on the status of my 8/31/26 request to increase the number of Strava users via my Strava-compatible running and cycling app - The Pace App (paceapp.net). Thank you  Edward KellyFounderThe Pace App 

Hi Strava Community & API Support Team,I am checking on the status of a Rate Limit Increase request submitted via the official form on August 31st for our non-commercial community application "Los retos de El Lobo" (Client ID: 175182)App Overview: Use Case: Non-commercial community cycling challenge leaderboard aggregation Authentication: OAuth 2.0 (activity:read / activity:read_all) Status: Currently operating with 10 authenticated test athletes on the Standard tier. Target: Scaling to 300 active participants for our upcoming challenge Architecture: Scheduled daily batch jobs via Make.com to avoid real-time API stress In our developer settings, the rate limits currently display "-1". Could an admin or team member please check if our submission is queued for review?Thank you for your assistance!Manuel (El Lobo de Las Hispanias)

Dear Strava Product & Engineering Team,I am writing to bring a major user experience gap to your attention regarding device identification on Strava activities, specifically for athletes using hardware via third-party sync applications.Right now, millions of users record activities on popular hardware like the Redmi Watch 3 Active, but because they sync through third-party companion apps, Strava completely overwrites the hardware brand with the software's name. This creates a frustrating disconnect for your users.Here is why resolving this should be prioritized in an upcoming update:Brand Pride & Social Proof: Strava’s core identity is built around sharing achievements and gear. Athletes want to showcase their actual watch brand (e.g., Redmi) on their feed. Masking the hardware behind generic software tags dilutes the visual appeal of the activity feed.Standardized Metadata Integration: Modern .FIT and .GPX files already contain distinct manufacturer and device_model data param

Hello,I maintain a personal training journal that imports my own Strava activities, and I want to check one point in the Developer Program terms before building the integration.The API FAQ states that "applications that expose athlete data to third party AI tools or use it in ways that conflict with our terms will not be approved." I would like to understand how broadly that applies.What the application does: at the athlete's explicit request, it sends that athlete's own activity data to a language model to produce a written summary, shown only to that same athlete. Nothing is used to train a model, nothing is shared with other users, and the model provider retains nothing for training.Scope: one user today — me — possibly my running coach and a few family members later, well inside the Standard tier's athlete limit. Not commercially available.Two questions:Does the restriction on exposing athlete data to third-party AI tools cover this kind of single-athlete, inference-only summary of

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

Hi Strava team and fellow developers,I’m building Unpack (unpack.fit), a personal training journal that lets athletes capture reflections by voice alongside their Strava activities.The idea is simple: after training, you might share your activity with your Strava community while wanting to keep a more personal account in your own journal, thinks like how you felt, what made the session difficult, or something you want to remember.We recognise that Strava already offers private notes. Our focus is the voice-first journaling workflow and revisiting those reflections over time, with a link back to the original Strava activity.Our integration is currently read-only. Our request to expand beyond 10 athletes was declined with the general response, and we’ve followed up with a clearer explanation of the complementary experience. We’re seeking an initial capacity of 100 athletes within Standard Tier, keeping our existing API rate limits.Have developers of similar companion apps successfully pa

Hi Strava team,Since the May strength update, exercises, sets, reps and weight can be logged in the app, but there doesn't appear to be any way to read that data back out. I've documented what I tested in case it's useful.What I tried:- GET /activities/{id} with activity:read_all. DetailedActivity returns description, laps, heart rate, calories, suffer_score. No exercises, sets, reps, total volume or muscle map.- The MCP connector (list_activities, get_activity_performance, get_activity_streams). Same result — nothing exercise-level.Request: could exercise-level data be exposed on read — either as fields on DetailedActivity or a dedicated endpoint such as /activities/{id}/sets? Even a summary (total volume, set count, muscle groups) would be useful for anyone building training analysis on top of Strava.Is this on the roadmap, or is there an existing route I've missed?Thanks.

Hi all,We are running an internal employee fitness challenge at 3Pillar Global, built on the Strava API (Client ID: 277940). Each employee connects their account via OAuth, and we aggregate their read-only activity data (activity:read + profile:read_all) into a team leaderboard and shared distance goal.We are currently on the Standard tier, onboarding toward the 10-connected-athlete threshold required before capacity review. Our target is approximately 500 employees for the full rollout.We have two questions for the community:Beyond the standard app-review process, is there a different track for this scale and use case (such as a paid tier or dedicated business contact), or does everyone go through the same review regardless of volume? Does anyone have advice or insights from scaling a similar single-org, read-only, self-connect app past a few hundred athletes?Thanks!

I'm building a read-only Strava application (Standard Tier, activity:read_all only, no write scope). It groups an athlete's own activities by distance, every half marathon, every century ride, and shows them side by side so the athlete can see how their performance has changed over time.That comparison is only meaningful across months and years, so the application caches each authenticated athlete's own activity data locally. Querying live per interaction isn't feasible within the rate limits.API Policy 6.2 states that Strava Data may not be retained in cache longer than seven days, and 6.4 limits retention to what is necessary for the original purpose. I can't find a carve-out for retaining an athlete's own data for the life of their account with a third-party application.Two questions:May an application retain an authenticated athlete's own activity data for as long as that athlete remains an active user of the application, where the sole purpose is presenting that athlete's own hist