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}/stats
I'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 as documented?
- Are there any other endpoints worth knowing about for a personal activity-sync use case like mine (e.g. gear, routes, segments) that I should plan for early, even if I don't need them at launch?
Thanks in advance — happy to share what I learn back here once I've built and tested it.
