Athlete capacity limit + revoke issue blocking Sydney Marathon runners

Hi Strava Developer Community,

We’re looking for help with a time-sensitive API issue affecting Pacelab (Client ID 255679).

We submitted our athlete capacity increase request about a week ago and it is still under review. Our current capacity is limited to 10 athletes, and new runners are already reaching Pacelab but are unable to connect their Strava accounts because the limit has been reached.

The timing is particularly difficult because the Sydney Marathon is on August 30. We built Pacelab to help runners understand a marathon course before race day — including the route, elevation profile and how the course can affect pacing. For Sydney, we are currently making this available for free because we wanted runners to be able to explore the course before the race.

We have already implemented proper authorization/deauthorization logic for one-time users: athletes who connect once and do not become ongoing Pacelab users are automatically deauthorized after a limited period, while active customers keep their Strava connection.

Unfortunately, we currently cannot even use this as a temporary way to recycle the available capacity. Some historical authorizations were created before this cleanup logic existed, and their current tokens are no longer available. At the same time, calls to the current /oauth/revoke endpoint are consistently returning HTTP 503, so we cannot reliably revoke those authorizations from our side.

Normally, while waiting for the capacity review, we could at least deauthorize one-time users after they have viewed their race analysis and allow the next runners in. Right now, we cannot do that either.

With Sydney now just over two weeks away, we would really appreciate any help from the Strava team with either:

• taking a look at our pending capacity review;
• temporarily increasing the athlete capacity while the review is in progress; or
• helping us clear the legacy authorizations / understand how we should proceed while /oauth/revoke is unavailable.

We’re happy to provide athlete IDs, timestamps, logs, or any other technical details privately if needed.

Our main goal right now is simply to let runners use the product before race day rather than turn them away because the first 10 slots are already occupied.

Thank you!
Pacelab