Skip to main content
Question

Rate Limit Increase Request Pending (Client ID: 175182) — Form Submitted Aug 31

  • September 14, 2026
  • 2 replies
  • 19 views
Forum|alt.badge.img+1

Hi Strava Community & API Support Team,

I am checking on the status of a Rate Limit Increase request submitted via the official form on August 31st for our non-commercial community application "Los retos de El Lobo" (Client ID: 175182)

App Overview:

  • Use Case: Non-commercial community cycling challenge leaderboard aggregation

  • Authentication: OAuth 2.0 (activity:read / activity:read_all)

  • Status: Currently operating with 10 authenticated test athletes on the Standard tier.

  • Target: Scaling to 300 active participants for our upcoming challenge

  • Architecture: Scheduled daily batch jobs via Make.com to avoid real-time API stress

In our developer settings, the rate limits currently display "-1". Could an admin or team member please check if our submission is queued for review?

Thank you for your assistance!

Manuel (El Lobo de Las Hispanias)

2 replies

Jan_Mantau
Forum|alt.badge.img+26
  • Jan_Mantau
  • Hub Powerhouse
  • September 14, 2026

Did your subscription run out in the last days? Also check that including make.com does conform to the API policy section 5.16 regarding third parties.

    Forum|alt.badge.img+1

    Hi ​@Jan_Mantau , thanks for the reply!

    1. Subscription & Pipeline Status: My Strava account subscription is active, and our Make.com integration pipeline is running smoothly with zero operation exhaustion or errors.

    2. Section 5.16 Compliance (Third Parties / Make.com):

      I fully adhere to Section 5.16 of the Strava API Policy:

    • Make.com is utilized strictly as our cloud backend / Integration Platform (iPaaS) to execute scheduled batch jobs and webhooks.

    • Make.com acts solely as a data processor in transit; no Strava data is shared with, sold to, or stored by third parties.

    • Data retrieved via OAuth 2.0 (activity:read / activity:read_all) is processed transiently to compute aggregated metrics (distance, elevation, moving time, dates) exclusively for our private challenge leaderboard hosted on Google Sheets.

    • No raw GPX data or personal identifying information is stored or transferred.

    We look forward to the Strava Developer Team reviewing our pending submission for Client ID: 175182. Thanks again for highlighting this!

    Terms & ConditionsAccessibility statement