• Replies 4 replies
  • Subscribers 14 subscribers
  • Views 543 views
  • Users 0 members are here
Options
Related

Discrepancies Between FIT Files from Garmin Connect and API (API Downgraded?)

pepe

Unfortunately, Garmin now applies extensive filtering to the files they serve via their API. This means the file retrieved through the API is not identical to:

  • The file you can manually download from Garmin Connect

What's being filtered?

 Garmin used to strip out workout steps from API-delivered files. However, based on recent observations, it appears Garmin have recently expanded extensively this filtering to include additional data elements—likely explaining the missing of several message numbers, session and lap fields we're now seeing.

  • I can confirm that this is already being discussed on the Intervals.icu forum as well, and honestly I find this quite unacceptable. (https://forum.intervals.icu/t/garmin-fit-fields-not-coming-in-possible-garmin-is-filtering-data-prior-to-sending-to-intervals-icu/124287)

    I am recording this data on an expensive Fenix 8X Sapphire, it is then synced into my Garmin Connect+ account, and after that Garmin appears to restrict what I can do with my own data once I want to process it further through the API. That is a very serious limitation for third-party platforms and for users who deliberately choose Garmin because of its broader ecosystem.

    In my view, this is not a minor technical detail. If data that is present in the original FIT file is being filtered out in the API version, that directly reduces the usefulness of external analysis tools and services.

    Could Garmin please provide an official statement on this? Is this an unintended bug or regression, or was this deliberately changed? If it was intentional, I would also strongly urge Garmin to reconsider and roll back these restrictions.

  • in reply to Hellkeeper

    We got an answer by Garmin "All messages and fields previously documented in the FIT SDK are still available. Undocumented messages and fields are being removed before files are sent to third-party platforms. "

    I hope DcRainmaker writes a blog post about it. (People: please ping him about it)

  • Sad to see this, I switched to Garmin just because of a good Intervals integration, now my switch becomes useless.

  • Update: dcrainmaker just posted this Info in the Intervals.icu Boards:
    -----

    The change was rolled back last night, while they take a deeper look at things.

    Behind the scenes, I’m continueing to push that the original FIT file is what’s sent. Never a special variant of it. To me, it’s the cornerstone of what Garmin initially promised at decade+ ago when sync first started happening.