What is a wearable API?

A wearable API lets your product read continuous physiological data from devices (and often write capture config) so your stack is the system of record, instead of forcing wearers into a separate consumer app.

How does a wearable API differ from a fitness data aggregator?

Aggregators stitch derived summaries from many consumer brands the wearer already owns. Device or platform APIs sit under hardware you brand and configure, with optional raw waveform access and one capture stack.

Does Sensor Bio provide raw PPG through its API?

Yes, when enabled for the organization. Partners can pull unfiltered green, infrared, and red amplitudes (when those channels are on) via batch export, REST at https://api.getsensr.io/v1/, and iOS/Android mobile SDKs. Sample rate is configurable at 25, 50, or 100 Hz (default 50 Hz). Confirm current field names on developers.sensorbio.com.

How does Sensor Bio compare to the Garmin Health API?

Garmin Health API (as of public developer docs reviewed 2026-10-27) delivers JSON summaries from data synced into Garmin Connect, with enterprise approval and optional enhanced beat-to-beat interval access. Sensor Bio is a device platform API: one hardware stack, org-level capture config, and optional raw PPG waveform export. Pick Garmin when your users already wear Garmin; pick a device platform when you need waveform control under your brand.

Is there a mobile SDK as well as REST?

Yes. Sensor Bio documents iOS (SPM) and Android (Kotlin Flow) BLE SDKs for device-adjacent sync, plus cloud REST for server-side workflows. Choose based on whether the phone is inside your trust boundary.

Who should use an aggregator vs a device platform API?

Use an aggregator when breadth across consumer devices is the product. Use a device platform when you need raw PPG, locked sample rates, white-label hardware, or operator tooling on one stack you control.

Wearable API for health products

Get Started