Hello Strava Developer Community and Strava API Team,
I’m reaching out on behalf of KASATI regarding our internal application, KASATI Running.
We previously contacted Strava Developer Support by email regarding an athlete capacity increase. We received an automated response advising us that athlete capacity and rate-limit increase requests are not reviewed by email and recommending that we post in the Developer Community Hub.
We would therefore appreciate guidance from the Strava team on the correct next step for our application review.
Application overview
Application: KASATI Running
Organization: KASATI
Use case: Private internal employee wellness and running program
Current athlete capacity: 10
Current connected athletes: 10/10
Requested capacity: Approximately 400 athletes/employees
Program start date: September 15, 2026
KASATI 41st Anniversary: October 10, 2026
KASATI Running is a private internal corporate wellness application developed for KASATI employees in Vietnam.
Employees voluntarily connect their individual Strava accounts using the official OAuth 2.0 authorization flow. The application uses authorized activity information to support employee wellness activities and internal event participation.
Our current athlete capacity has already reached 10/10, so additional employees are currently unable to connect their Strava accounts.
We expect approximately 400 employees to participate in our internal running and wellness program. The program begins on September 15, 2026 and forms part of the activities leading up to KASATI’s 41st anniversary on October 10, 2026.
Compliance and technical implementation
We are committed to complying with the Strava API Agreement, API Policy, and Brand Guidelines.
Our application includes:
- OAuth 2.0 authorization for each athlete
- User-controlled Strava disconnect
- Data deletion request functionality
- Public Privacy Policy
- Public Support / Contact page
- HTTPS
- Secure OAuth token storage
- Role-based access control
- Webhook-based processing where appropriate
- Controlled synchronization to minimize unnecessary API requests
KASATI Running does not sell, resell, or monetize Strava data.
We are also willing to make any application changes required by Strava to ensure full compliance before expanded athlete access is granted.
Our request
We would greatly appreciate assistance with one of the following:
- Confirming that our Developer Program review request is in the appropriate queue;
- Advising us how to request an athlete capacity increase from 10 to approximately 400 athletes;
- Letting us know if any additional screenshots, technical documentation, privacy documentation, or compliance information is required;
- Advising whether there is any official business, partnership, subscription, or commercial program appropriate for this corporate use case.
We are not requesting any circumvention of Strava’s API limits or review process. We want to follow the official process and ensure the application remains fully compliant.
Because our employee program is scheduled to begin on September 15, 2026, we would be extremely grateful for any guidance or assistance that could help us complete the review as soon as possible.
Website:
https://erp.kasati.com.vn/running/
Privacy Policy:
https://erp.kasati.com.vn/running/privacy.php
Support:
https://erp.kasati.com.vn/running/contact.php
We can provide our Client ID and any additional application details privately to the Strava team if required.
Thank you very much for your time and support.
Best regards,
KASATI Running Team
KASATI
Vietnam