Clarification needed: How to handle API access for a club with ~80 athletes after removal of club endpoints

Hi everyone,

I’m the developer for a cycling club application used by 5071 Cykleklubb in Norway. We have around 80 active members, and until recently we relied on the Strava V3 API’s club endpoints to generate internal statistics, yearly totals, and non‑public dashboards for our members.

After the September 2026 removal of the club endpoints, we understand that the only compliant way to continue is through individual athlete authorization using /athlete/activities.

However, when onboarding members, our application now hits:

Code

Error 403: Limit of connected athletes exceeded

I’ve contacted Strava support, but they directed me here for API‑related guidance.

What I need clarification on:

1. Is there any supported method for clubs or organizations to connect more than the default number of athletes to a single API application? (Our use case is strictly internal, non‑commercial, and does not expose or redistribute athlete data.)

2. Is there an organizational or enterprise API tier that allows higher athlete connection quotas? The bulk subscription program seems unrelated to API access.

3. If the quota cannot be increased, what is the recommended approach for clubs that previously relied on club endpoints for internal statistics? Splitting into multiple apps is technically possible but impractical for long‑term maintenance.

Additional context:

• We do not store or share athlete data outside the club environment.

• We only need read access to activities for internal statistics and training program support.

• We are not building a public platform or commercial service.

• We are simply trying to replace the functionality that was lost when club endpoints were deprecated.

Any guidance from Strava engineers or other developers who have handled similar transitions would be greatly appreciated.

Thanks in advance.

Stian