still there, for some reason
Fit file message number 79, 140 and 147 gone, and many message number 18,19 and 20 fields gone.
assume 1 file saves 50kB
The API sends out say, 1 million per day = 50MB
Doesnât seems like much savings
I donât think theyâre doing it for the bandwidth saving reasons.
If Garmin intentionally removes those fields - they remove âtheirâ, or proprietary calculated fields and leave access only to âyourâ data (HR, GPS, Pace, Power). Basically you get access only to what youâve uploaded to Garmin.
I agree. It seems more likely to be about directing user traffic than about saving bandwidth on responses to API calls. Users will go to Garmin Connect to the extent that it presents information that they canât see anywhere else.
That would be somewhat understandable if not for how limited connect is. Rounding, lack of custom charts and tables⌠A lot not within control of the user.
Well, maybe just the next step to âforceâ people into their subscription model
Itâs frustrating that the fields are still there if I export from Garmin Connect myself thoughâŚ
I wonder if things are different for other platforms, like TP for exampleâŚ
wouldnât phrase it like that ⌠I would say: Thank god (Garmin?!?) that they are still there in the manual export âŚ
quote
[mipapo ]Discrepancies Between FIT Files from Garmin Connect and API (API Downgraded?) - Discussion - FIT SDK - Garmin Forums) 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)â
Uggghhhh yeah I guess but itâs created a chore I didnât have a week agoâŚ
Just adding to thisâmessage 147 is a clear example.
Garmin isnât just removing proprietary fields. Theyâre stripping out user administered sensor settings like:
Sensor name
Crank length
Wheel size
Footpod Calibration factor
"Use for speed/distance" toggle
These arenât Garmin-calculated metricsâtheyâre settings users configured to ensure accurate data. Without them, we lose critical context for interpreting power, torque, speed, and distance.
Not sure if anything changed in the Garmin API, but I just came back from a run and I see a VO2max value populated now 
VO2 max can be present in the FIT file or sent via the API
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.
Hey Ray,
Itâs great to see you looking into this â thanks for the update, and welcome to the board! 
I really hope Garmin will continue to make all of the data available in the long term, since itâs the foundation of what has grown into a pretty large ecosystem by now.
Thanks again,
best regards from Tyrol,
Andreas
To confirm coming the fields are coming through fine for me from my run at lunch time today.
Thanks to our new celebrity member for any advocating done on our behalf!
Hi.
I was having the same issue yesterday.
My rides are ok in Garmin, but here, I am missing a lot of dats.
Generated the FIT file from Garmin and imported manually here, same.
I will have a look today after my ride if this is still ongoing
Any news on that matter?