Wearable API
The wearable health data API, with the hardware underneath.
Sensor Bio is a wearable data API for teams that build health products and run studies. One band, a REST API, iOS and Android SDKs and raw multi-wavelength PPG, all on one stack you can put your brand on.
- REST API
JSON for sleep, biometrics, scores and activity.
- Mobile SDKs
iOS and Android. Live streams and background sync.
- Raw PPG
Green, red and infrared, unfiltered.
- Your config
25, 50 or 100 Hz, set per organization.
- Sensor Bio V2
No screen. 5 to 7 days per charge.
What a wearable data API gives you
A wearable data API moves continuous physiological data from a device into software you run. Sensor Bio pairs its own band, Sensor Bio V2, with a REST API for sleep, heart rate, HRV, SpO2, breathing rate, scores and activity, mobile SDKs for live streams, and raw green, red and infrared PPG for your own algorithms.
- REST API for your backend: JSON per member and per organization.
- Mobile SDKs for your app: pairing, live streams and background sync on iOS and Android.
- Raw data for your algorithms: unfiltered PPG and accelerometer files.
- The Remote Monitoring Dashboard when your team wants no code at all.
Which data comes through which path
Most teams start with the REST API and add the SDK when the phone is part of the product. Raw files are for teams that run their own signal processing.
| Data | REST API | Mobile SDK | Raw download |
|---|---|---|---|
| Sleep and sleep stages | Yes | On-device staging, synced | No |
| Heart rate | Yes | Live stream | Derive it yourself |
| HRV | Yes | Live stream | Derive it yourself |
| SpO2 | Yes | Live stream | Derive it yourself |
| Breathing rate | Yes | Not streamed | Derive it yourself |
| Beat-to-beat intervals | No | Live stream | Derive it yourself |
| Signal quality | No | Live stream | No |
| Scores, recovery, steps, calories, activities | Yes | Not streamed | No |
| Raw PPG (green, red, infrared) | No | Raw stream | Yes |
| Raw accelerometer (x, y, z) | No | No | Yes |
| Users, invites, device lock | Organization endpoints | No | No |
Aggregator API or device platform
Wearable APIs come in two shapes. An aggregator pulls summaries from consumer devices your users already own. A device platform sits under hardware you deploy, so you control capture and keep the raw signal. Sensor Bio is the second kind.
For the long version, with the questions to ask any vendor, read Wearable API for health products.
| Aggregator API | Device platform (Sensor Bio) | |
|---|---|---|
| Where the data comes from | Consumer devices your users already own, through each brand's cloud | One band you deploy, configure and brand |
| What you usually get | Daily summaries and scores in a common format | Summaries, live streams and the raw waveform behind them |
| Control of capture | Set by each device maker | Sample rate, wavelengths and duty cycle set per organization |
| Brand the wearer sees | The device maker's app sits next to yours | Your app, your dashboard, your report emails |
| Best fit | Breadth across many consumer brands is the product | You need raw signal, one hardware stack and your own brand |
Raw multi-wavelength PPG
Most wearable APIs stop at the score. Sensor Bio V2 also hands over the waveform behind it.
- Green, red and infrared LEDs at 530, 655 and 940 nm, read by two photodiodes.
- Unfiltered PPG columns ts, green, ir and red, plus accelerometer x, y and z.
- 25, 50 or 100 Hz, with 50 Hz as the default. Raw capture is off by default and turned on per organization.
- Delivered through the SDK raw stream and a per-organization download. See how raw PPG access works and how PPG works.
Sensor configuration
Capture settings decide what your API can return. Sensor Bio configures them for your organization, white-glove. The default is 50 Hz green PPG for 45 seconds every 5 minutes. The sensor configuration page lists every option, with a downloadable spec sheet.
From first call to live data
Four steps. The reference for every endpoint and SDK call lives on developers.sensorbio.com.
Step 1
Scope it with us
Book a demo. Tell us what you are building, which data you need and how often. Demo credentials for the API are available on request.
Step 2
We configure your sensors
Sensor Bio sets sample rate, wavelengths and capture windows for your organization, white-glove, and for individual devices where your protocol needs it.
Step 3
Issue your keys
Create an organization API key in the web platform for server-side calls. SDK keys stay on your backend and are exchanged for a single-use token that signs a member in to your app.
Step 4
Stream, pull or download
Use the SDK for live data in your app, the REST API for server jobs and warehouses, and the per-organization download for raw files. Sample code ships in curl, Python, TypeScript and Go.
Who builds on it
Teams that need continuous physiological data inside their own product, study or program. See also wearables for clinical trials and how to choose a research wearable.
Digital health products
Put continuous HR, HRV, SpO2 and sleep under your own app instead of sending people to someone else's.
Research teams and CROs
Locked capture settings, raw waveforms and wear-time data you can audit across a whole cohort.
Algorithm and model teams
Unfiltered green, red and infrared PPG at up to 100 Hz to train and test your own methods.
Workforce and safety programs
Overnight sleep and recovery trends across shifts and sites, routed into the tools you already use.
Coaching and performance
Readiness and recovery data in your coaching platform, with your thresholds.
White-label partners
Your brand on the app, the web dashboard and every email, with the API and SDK underneath.
How V2 compares
Side-by-side pages for the wearables teams ask about most, with sources and dates on every spec.
Questions, answered.
What is a wearable health data API?
It is the interface that moves physiological data from a wearable into software you run, such as sleep, heart rate, HRV, SpO2 and breathing rate. Sensor Bio provides a REST API and iOS and Android SDKs for data from Sensor Bio V2, plus raw PPG for teams that run their own algorithms.
What data does the Sensor Bio API return?
Per member: sleep, biometrics (heart rate, SpO2, breathing rate and HRV), scores, recovery, steps, calories, activities, device info and insights, as JSON. Per organization: users, invites, sign-up, login tokens, device lock and device subscriptions.
Can I get raw PPG data?
Yes. Raw green, red and infrared PPG comes through the Mobile SDK raw stream and a per-organization download from the web platform. Raw capture is off by default and enabled per organization. Raw export through the REST API is not available for V2 today.
Is there an SDK for iOS and Android?
Yes. The iOS SDK installs with Swift Package Manager and the Android SDK from Maven. Both handle pairing, live streams of heart rate, HRV, SpO2, signal quality, beat-to-beat intervals and raw PPG, and background sync.
How is this different from a wearable data aggregator?
An aggregator pulls summaries from consumer devices your users already own. Sensor Bio is a device platform: one band you deploy and configure, with summaries, live streams and the raw waveform on one stack under your brand. Read the full guide in The Signal.
How do we authenticate?
Server-side calls use an organization API key created in the web platform. Apps that act for a member use OAuth2 with refresh tokens, and SDK keys stay on your backend, where they are exchanged for a single-use token.
Can we put our own brand on it?
Yes. Your app sits on the SDK and API, and the Sensor Bio web dashboard, app and report emails can carry your brand.
Is Sensor Bio V2 a medical device?
No. Sensor Bio V2 is a general wellness device and is not FDA cleared. The API delivers wellness and research data. It does not diagnose.
Protect the Signal.
Put continuous physiological data under your product.
Book a demo and we will scope the data, the capture settings and the first integration with your team.
Sensor Bio V2 is a general wellness device. It is not FDA cleared and is not intended to diagnose, treat, cure or prevent any disease. Data described on this page is for wellness, research and product development use.