How to Obtain Wearable Data for Research or Healthcare
“We’re sorry, but this will require additional cost and effort on your side.”
This unexpected reply leaves many researchers surprised when they contact wearable manufacturers with a seemingly simple question: How do I access the data from my recently purchased devices?
Let’s start from the beginning.
Why Consumer Wearables?
Consumer wearables offer a cost-effective and scalable alternative to traditional medical devices for collecting physiological data. Their affordability enables studies with larger participant groups, while their appealing design leads to higher acceptance and longer wear times among users—crucial factors in any data-driven study.
The Common Process (and the Pitfall)
Most research projects begin with a market analysis to identify suitable wearable devices. Well-known brands like Garmin, Apple, Google, Oura, Fitbit, and Whoop are quickly shortlisted. Often, researchers gravitate toward the device they use personally, assuming that the same data access they have for themselves will be available for their study participants.
After identifying the preferred device, pricing is typically straightforward—consumer wearables are widely available online, making costs transparent. With this, researchers proceed to apply for funding through grants and, once approved, purchase the devices directly from manufacturers or online retailers.
So far, everything seems on track.
The Reality Check
During the test phase—usually with colleagues—researchers quickly discover a major limitation: accessing data from anyone other than the device owner is extremely difficult. That’s because consumer wearables are built for individual use and personal health tracking. There is no “researcher mode” or native support for centralized data access from multiple users.
This leads researchers to contact manufacturers directly, only to find three typical options—none of which are ideal:
1. API/SDK Access – Often free, but requires significant development effort and technical expertise. Data access is frequently limited or restricted to low-resolution metrics.
2. B2B Dashboards – Offered at additional cost, these often lack the flexibility and features needed for in-depth research.
3. Third-Party Platforms – Provide enhanced functionality but also come with extra costs and licensing requirements.
Unfortunately, these unanticipated technical and financial demands are often not accounted for in the original project funding—causing delays or even derailing entire projects.
The Fitrockr Solution
At Fitrockr, we frequently receive calls from researchers facing exactly this situation. They assumed data access would be simple and free—just like it is for personal use. Sadly, it’s not.
That’s why we developed the Fitrockr Research & Health Platform—to bridge this critical gap. Fitrockr offers a plug-and-play solution for managing and collecting data from multiple wearables, without the need for software development or licensing manufacturer dashboards with just basic functionality.
Whether you’re in research, healthcare, or clinical trials, Fitrockr simplifies wearable data collection and makes it project-ready.
Device-Specific Data Access Overview
Below is a summary of how to access data from popular wearables—along with how Fitrockr can help:
Garmin
– Web API: Free, but requires development and offers limited data (e.g. no raw HRV/BBI).
– SDK: High license cost, complex development needed (iOS/Android app required), access to high-resolution data.
– Fitrockr: Full plug-and-play access to high-resolution Garmin data.
Withings
– Web API: Free, requires development.
– Dashboard: Paid option with limited features.
– Fitrockr: Full plug-and-play access to all Withings data, no development required.
Apple Watch
– SDK: Free, requires mobile app development.
– Fitrockr: Full plug-and-play data access, no development needed.
Google Pixel Watch
– SDK: Free, requires mobile app development.
– Fitrockr: Full plug-and-play data access, no development needed.
Fitbit
Google plans to discontinue Fitbit. We do not recommend starting new projects with Fitbit devices.
Whoop
– Web API: Free, requires development.
– Dashboard: Paid option, limited in scope.
– Fitrockr: Integration available on request.
Oura
– Web API: Free, requires development.
– Dashboard: Paid B2B dashboard with limited features.
– Fitrockr: Integration available on request.
All information above is provided without warranty and may change at any time.
Final Thoughts
If you’re planning a wearable study, we highly recommend understanding the data access options before finalizing funding or making purchase decisions. This guide is intended to help you make informed choices early in the process.
If you have already obtained funding but do not know how to access the data, let us know.
Contact us — we’re happy to advise, even if you’re not planning to use our platform.