Migrate a Strava API integration to the new api-v3.strava.com base URL ahead of the January 2027 cutover

domain: developers.strava.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Read the official Strava V3 API changelog entry dated June 1, 2026 confirming the base URL is changing from https://www.strava.com/api/v3 to https://api-v3.strava.com
  2. Note the new base URL becomes available starting January 4, 2027 — plan the cutover but do not hardcode the new host before that date
  3. Update all HTTP client base-URL configuration and any hardcoded https://www.strava.com/api/v3 references to point at https://api-v3.strava.com once available
  4. Adopt the new deauthorization endpoint documented alongside this change under the authentication docs
  5. If your app depends on Club Activities, Club Members, or Club Admins endpoints, plan removal/replacement before September 1, 2026 when they are removed
  6. If your app uses Explore Segments, confirm you hold Extended Access Tier before September 1, 2026, when that endpoint becomes restricted

Known gotchas

Related routes

Create a Strava webhook subscription and handle push events for activity and athlete changes
developers.strava.com · 5 steps · unrated
Migrate an AWS SDK for JavaScript v2 integration to v3 before end of support
docs.aws.amazon.com · 5 steps · unrated
Migrate a Tripleseat integration from OAuth 1.0 to OAuth 2.0
api.tripleseat.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans