Skip to main content
Question

Athlete Limit Increase request (Client ID: 197044) | Decode Strength

  • May 18, 2026
  • 0 replies
  • 1 view

Forum|alt.badge.img

Hello Strava Developers Team,

Requesting an athlete cap increase for Decode Strength (Client ID: 197044).

What it does: Every athlete gets a public performance profile at their own URL — name.decodestrength.com — showing fitness trajectory, race history, personal bests, readiness trends, and a running archetype built from their Strava data. A live portfolio page a runner would actually put in their bio. See it: decodestrength.com/demo

API usage:

  • Scope: activity:read_all only. No write scopes.
  • Initial backfill via /athlete/activities, then fully webhook-driven — no polling.
  • Stored fields: activity_idsport_typedatedistancedurationpacehr_avg/maxelevation. No GPS, no social data.

Compliance:

  • Tokens refreshed only within 60s of expiry; latest refresh_token always persisted.
  • In-app disconnect immediately wipes all tokens and connection records.
  • Strava branding guidelines followed throughout.
  • Athlete data used solely to power their own dashboard — never shared or sold.

Scale: Targeting 200-500 runners in the first 6 months as athletes share their public dashboards.

Happy to provide a demo account or screenshots if helpful.

Shriniwas Decode Strength — decodestrength.com