Skip to main content
Answered

How do we move from 1 connected athlete to production quota?

  • February 12, 2026
  • 5 replies
  • 268 views

Forum|alt.badge.img+1

Hi everyone,

 

I’m currently building an application that integrates with the Strava API primarily for athlete verification and limited profile display (recent activity summary, ride count, etc.).

 

The OAuth flow is working correctly and tokens are stored securely. However, the application is currently limited to 1 connected athlete, and additional users receive:

 

Error 403: Limit of connected athletes exceeded

 

I’m trying to understand the correct process to move from development (1 athlete) to production-level athlete limits.

 

I don’t see a “Request Production Access” option in the API dashboard. Is the current process to submit a support ticket, or is there another mechanism for requesting a quota increase?

 

For context:

 

  • We are not replicating Strava features.
  • We only request basic read scopes.
  • Users can disconnect at any time.
  • We comply with Strava’s branding and data usage guidelines.

 

 

Any guidance from developers who’ve recently gone through production approval would be greatly appreciated.

 

Thanks in advance.

Best answer by Jana_S

Hi ​@Louishall, you need to submit the Developer Program form linked from the following page: https://developers.strava.com/docs/rate-limits/

5 replies

Jana_S
Forum|alt.badge.img+29
  • Hub Superuser Alumni
  • Answer
  • February 12, 2026

Hi ​@Louishall, you need to submit the Developer Program form linked from the following page: https://developers.strava.com/docs/rate-limits/


Forum|alt.badge.img+1
  • Author
  • Hub Rookie
  • February 13, 2026

Thank you Jana!!


Forum|alt.badge.img
  • Hub Starter
  • May 15, 2026

Merlo Bike is a bicycle shop management application used by a physical bike shop in Brazil. The application integrates with the Strava API to provide a customer-facing service that improves bicycle maintenance through real activity data.

The app uses Strava data solely to:

  • Calculate accumulated distance per bicycle

  • Display recent athlete activities within the user account

  • Generate preventive maintenance recommendations based on usage

This functionality is directly tied to the athlete’s own data and provides a clear, individual user benefit.

Authorization Flow:

All athletes connect their Strava accounts through the official OAuth flow.

  • Access is explicitly granted by the user

  • Users can revoke access at any time via Strava

  • No data is accessed without user authorization

Scopes Requested (Least Privilege Principle):

  • activity:read — to access activity data required for distance calculations

  • read — to identify the authenticated athlete

We only request scopes strictly necessary for the described functionality.

Data Handling and Compliance:

  • We do not sell, sublicense, or redistribute Strava data

  • Data is only accessible to the authenticated user within their account

  • We do not expose data publicly or to other users

  • We store only the minimum data required to deliver the service

  • All usage complies with Strava API Agreement and Brand Guidelines

Use Case Justification:

This is a service integration where Strava activity data is used to improve equipment maintenance, safety, and user experience. The application does not replicate Strava functionality but extends it with a complementary, real-world service.

Expected Usage:

We expect approximately 200–500 athletes to authorize the application. The system is already in production use internally and ready to onboard users immediately upon approval.

Platform Relationship:

The integration supports the Strava ecosystem by encouraging athletes to maintain their equipment properly, promoting continued activity and long-term engagement.


Forum|alt.badge.img
  • Hub Starter
  • May 15, 2026

 


Jan_Mantau
Superuser
Forum|alt.badge.img+27
  • Superuser
  • May 15, 2026

Hi ​@Felipe Merlo , what is the aim of your post?