For the complete documentation index, see llms.txt. This page is also available as Markdown.

Why did old Garmin payloads arrive without my request?

This is expected behaviour given Garmin's API design, not an error on your side.

This is expected behaviour given Garmin's API design, not an error on your side.

Why it happens:

  • Garmin delivers data asynchronously, with no reference tying it back to the originating request.

  • A single end user can be connected to several Terra-powered apps, and Garmin also pushes some historical data automatically (for example, via planned-workout polling).

  • If another app requests years of history, Garmin pushes it and Terra must forward it to every connected app. This surfaces as thousands of unrequested or pre-connection-date historical payloads.

Deduplicate on your side using summary identifiers and timestamps. See receiving data updates for how payloads arrive.

Last updated

Was this helpful?