12-30-2025 12:47
12-30-2025 12:47
When requesting the TCX for a structured workout (recorded on a Pixel Watch 4) the data does not show the laps from the structured workout, but instead just returns a lap for each kilometer (1000.0m).
For example in an interval training consisting of 5 800m intervals, I'd expect the API to return 5 laps with a distance of 800m, instead only 4 laps are returned, and the distinction between the intervals is pretty much impossible to detect from the API alone.
The workout is created using the Fitbit app and recorded with a Pixel Watch 4. In the Fitbit app itself the data is shown with the correct intervals.
01-06-2026 13:32
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
01-06-2026 13:32
Hi @inukiwi
Welcome to the community!
Thanks for sharing your question. Please let us check it and will get back to you as soon as we can.
Best Answer01-13-2026 13:51 - edited 01-13-2026 13:51
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
01-13-2026 13:51 - edited 01-13-2026 13:51
Hi @inukiwi
Thank you for your patience while we looked into this.
Regarding the lap data and the distinction between intervals (active vs. resting), as stated in the documentation, “Intensity” only returns the 'active' splits. 'resting' splits is not supported or returned by the response.
Additionally, the laps in the TCX export are generated based on standard distance splits (such as 1km) rather than the specific interval boundaries defined in a structured workout. We understand how having these intervals reflected in the API is important for your training analysis. I have created a support ticket and documented your feedback for our engineering teams to review. I will provide updates here if I hear anything further.
Best Answer