Strava API
GET /api/v3/clubs/{id}/admins endpoint removal
Stopped workingSubscribe to Strava APIShare
On September 1, 2026, GET /api/v3/clubs/{id}/admins was removed. Requests to this endpoint fail since that day. The change followed an announcement that club activities, club members, and club admins endpoints would be retired.
Calls it hits
GET /api/v3/clubs/{id}/admins
What to use instead of these calls
There is no replacement for reading club admins, so you must drop the call. The endpoint GET /api/v3/clubs/{id} still returns the club itself.
Strava offers no replacement for reading a club's activities, members or admins.
In Strava API's words
Club Activities, Club Members, and Club Admins endpoints will be removed on September 1, 2026
Facts
- API
- Strava API
www.strava.com - Kind
- Endpoint removal
- Announced
- June 1, 2026
- Takes effect
- September 1, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Strava API's own pages
Questions
When does this change take effect?
Calls to GET /api/v3/clubs/{id}/admins on Strava API stopped working on September 1, 2026.
What happens to calls after September 1, 2026?
They have failed since September 1, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Strava API 5
-
GET /api/v3/clubs/{id}/activitiesEndpoint removal Stopped working -
GET /api/v3/clubs/{id}/membersEndpoint removal Stopped working -
GET /clubs/{id}/activitiesRemoval Stopped working -
GET /clubs/{id}/adminsRemoval Stopped working -
GET /clubs/{id}/membersRemoval Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.