Hi everyone,
I’m working on a website that integrates with the Strava API to display user activity data such as recent rides, runs, distances, and timestamps. The integration generally works, but I’ve started running into issues where the data returned by the API is either incomplete or delayed compared to what users see directly on their Strava accounts.
In particular, newly uploaded activities don’t always appear on my website immediately, even though the access token is valid and the API request completes successfully. In some cases, older activities load correctly while the most recent one is missing, or certain fields (like elapsed time or elevation data) come back as null or outdated. This makes the frontend display inconsistent and confusing for users.
I’ve verified that the app is using the correct scopes during OAuth authorization and that rate limits aren’t being exceeded. I’m also handling token refresh properly and storing refreshed tokens as expected. From the API logs, the requests look successful (200 responses), but the data itself doesn’t always match what’s shown in Strava’s UI.
Is this expected behavior due to activity processing delays, caching, or API update timing? Are there recommended best practices for keeping website data in sync with Strava, such as relying more on webhooks or specific endpoints? I’m happy to share more details about the API calls or app setup if needed.
