
How to add wearable data to your app with a white-label wearable
A step-by-step white-label wearable integration guide: what the setup involves, the shortest path to wearable data in your app, and how small teams start without engineers.
Quick answer: To add wearable data to your app with a white-label wearable, you scope the data you need, have the wearable maker configure capture for your organization, put your brand on the band, and wire its SDK and API into your product. With Sensor Bio, that means Sensor Bio V2 under your brand, a REST API for sleep, heart rate, HRV, SpO2 and activity, iOS and Android SDKs for live streams, and optional raw PPG. Teams with no engineers can start on a no-code dashboard.
Most teams that ask how to add wearable data to an app have already tried the obvious route. They connected a few consumer devices, got daily summaries, and then hit a wall: the data follows someone else's roadmap, the wearer sees someone else's app, and nobody can say what is under the score.
A white-label wearable fixes the first two problems by putting your brand on the hardware. A platform with raw signal access fixes the third. This guide walks the setup from first call to launch, so you know what the work is before you book the demo.
Three ways to put wearable data in an app
There are three honest options, and they suit different jobs.
An aggregator API. One integration reads summaries from consumer devices your members already own. It is the fastest way to a demo when breadth across brands is the product. You get what each device maker chooses to share, usually daily summaries, and the wearer keeps using that maker's app.
A device platform under your brand. You deploy one band, configure what it captures, and read the data through an SDK and API. The wearer sees your app, your dashboard and your emails. This is the white-label path, and it is the subject of this guide.
Your own hardware. You design sensors, firmware, Bluetooth, batteries and manufacturing yourself. It gives total control and takes years before the first person wears a band.
If you are still choosing between the first two, read Wearable API for health products. It compares aggregators and device platforms in detail. The rest of this guide assumes you want your own branded band.
What a white-label wearable integration includes
On Sensor Bio, the stack comes in five pieces. You can use one or all of them.
| Piece | What it does | Who uses it |
|---|---|---|
| Branded hardware | Sensor Bio V2 with your logo, strap color and packaging | Your members |
| Mobile SDK | iOS and Android pairing, live streams and background sync | Your app team |
| REST API | Sleep, biometrics, scores and activity as JSON, per member and per organization | Your backend team |
| Algorithms | Ready-made wellness algorithms, or your own on raw data | Your data team |
| Remote Monitoring Dashboard | A no-code view of your whole program | Coaches, program staff, support |
The band itself has no screen. It lasts 5 to 7 days per charge under default settings and stores about 14 days of data on the device at default settings, so a missed sync does not mean missing data. SpO2 is live today alongside heart rate, HRV, breathing rate, sleep and activity.
For the full picture of the white-label offer, see the white label wearable page.
The setup, step by step
Here is the order the work happens in. None of it requires your team to write firmware.
1. Scope the data you need
Start with the product, not the sensor. Write down what your app will show, what your team will act on, and how often the data has to arrive. A sleep coaching app needs nightly sleep and an HRV trend. A study team may need raw waveforms it can reopen later. A workforce wellness program may only need overnight recovery trends by shift.
That list decides almost everything that follows: which stack pieces you need, how the band is configured, and whether raw capture is on.
Bring the list to a demo call. Demo credentials for the API are available on request from the developer team, so your engineers can read real response shapes while you scope.
2. Let Sensor Bio configure capture
Capture settings decide what your API can return. Sensor Bio sets them for your organization, white-glove, and for individual devices when your program needs it.
The defaults are a sensible starting point. PPG samples for 45 seconds every 5 minutes. The accelerometer runs all the time at 50 Hz. PPG sampling can be set to 25, 50 or 100 Hz. Raw PPG capture is off by default and turned on per organization, and raw accelerometer streaming is a configuration option too.
Higher sampling rates and raw capture use more battery and on-device storage. Choose them because your analysis needs them, not because they are the maximum. The sensor configuration page lists every option, and how to configure a research wearable explains the tradeoffs.
Lock these settings before the first person wears a band. Changing capture halfway through a program makes early and late data hard to compare.
3. Brand the band and the box
Your logo, strap color and packaging go on Sensor Bio V2. Order minimums are agreed with the Sensor Bio team during scoping. Your brand can also carry through the Sensor Bio app, the web dashboard and report emails, so the wearer never meets a second brand.
4. Issue keys and wire the integration
Engineering work starts here, and it is smaller than most teams expect.
- Server side. Create an organization API key in the Sensor Bio web platform. Your backend uses it to call the REST API for members, invites, device lock and per-member data.
- Member consent. Apps that act for a member use OAuth2 with refresh tokens.
- Mobile. The iOS SDK installs with Swift Package Manager. The Android SDK comes from Maven. Your SDK key stays on your backend, where it is exchanged for a single-use token that signs a member in to your app.
- Pairing. Pairing a band is one transaction in the SDK. After that, background sync runs on its own, with on-device processing for HRV, sleep staging and activity.
- Samples. Developer samples ship in curl, Python, TypeScript and Go.
Every endpoint and SDK call is documented on Developers.
For product and program teams
Put the raw signal in your study or product
Bring your data list to a demo. We will map it to the stack pieces, the capture settings and the first integration step with your team.
5. Pilot small, then launch
Run a short pilot with a small group before the full launch. Check three things: that members can pair and charge without help, that the data your app shows matches the data your team expects, and that your support staff know where to look when a band stops syncing. The dashboard shows wear time and sync status for each member, which makes that last check quick.
Then launch, and add features over time. Many teams start with the branded band and SDK and add raw data, algorithms or the dashboard as the product grows.
The shortest path to wearable data in your app
If speed matters most, match the path to the job:
- You only need daily summaries in your product. Use the REST API from your backend. No mobile work.
- The phone is part of the experience. Add the SDK for live heart rate, HRV, SpO2, signal quality and beat-to-beat intervals in your app.
- You run your own algorithms. Turn on raw capture and use the SDK raw stream or the per-organization download. See raw PPG access for the file formats.
- You have no engineers yet. Start on the dashboard and downloads, below.
You can move between these without changing the band. That is the main advantage of owning the device layer.
Starting without an engineering team
Small coaching practices, wellness programs and early product teams often have the idea before they have engineers. They can still run a program.
The Remote Monitoring Dashboard is a no-code web app for running a wearable program. Here is what a small team gets without writing code:
- One table for everyone. Last night's wear time, sleep, HRV, resting heart rate, SpO2, breathing rate and skin temperature for every member, plus daily activity and 30-day trends per member.
- Bulk invites. Invite a whole group at once from a CSV.
- Adherence on your rules. Set daily rules such as hours worn and a recorded sleep, and see who is on track, at risk or off track.
- Alerts. Signal Studio sends a push or email to the member, to staff, or both, when a metric crosses a threshold your team defines.
- Reports and exports. Scheduled daily or weekly report emails with CSV attachments, computed metrics downloads as CSV or JSON for 1 to 30 days per request, and raw data for 1 to 7 days when raw capture is on.
When engineers join, they build on the same organization, the same bands and the same data. Nothing is thrown away.
Questions to settle before you sign
Use this list with any white-label wearable vendor, including us.
- Which data comes through the API, which through the SDK, and which only as raw files?
- Can we get the raw waveform, and is it on by default?
- Who sets sample rate and capture windows, and can they be locked per organization?
- How long does the band last per charge, and how much does it store between syncs?
- Whose brand does the wearer see in the app, the dashboard and the emails?
- What does the product claim, and does it match the device's regulatory status?
That last question matters. Sensor Bio V2 is a general wellness device and is not FDA cleared. FDA's general wellness policy covers low-risk products that support a healthy lifestyle, and it shapes what a product built on the band can say. Keep your claims to general health and wellness, and Sensor Bio's team will share claim guidance during launch.
Where to go next
Read the wearable data API page for what each path returns, or the white label wearable page for the full offer. When your data list is ready, Get started and we will scope it with you.









