$3,500 per platform, and what makes it hard
Pick the platforms your users wear. Each has a documented behaviour that costs engineering time, such as silent permission denials, partial deduplication or membership-gated metrics, and the calculator shows it next to the price so it doesn’t surprise you in month two.
Estimated range
$7,000
2 platforms at the published $3,500 each. A straightforward read is the published price with no multiplier on top.
- Apple HealthKit
- $3,500
- Android Health Connect
- $3,500
This range excludes
- The app the data flows into (this is the integration only)
- Developer-programme access fees or agreements a vendor may require
- Test hardware. Real-device QA needs the actual devices
- Aggregator subscription fees, which are quoted by volume
Platform notes checked against vendor documentation, September 2026.
Where the time goes
Four things that cost more than the API call
Reading a step count is a morning’s work. Everything below is the rest of the project.
Deciding which data counts
Several apps write steps to the same store, so you have to decide which one is authoritative and whether the platform dedupes for you. Health Connect does it only for Activity and Sleep; everything else silently sums.
You often cannot know what you were denied
HealthKit will not tell you a read permission was refused; the data just appears absent. Products that assume denial is detectable ship a broken empty state to some of their users.
Background delivery has its own rules
Entitlements, frequency caps and observers that get cut off after repeated failures. This is where 'it worked in testing' turns into 'the data stops arriving on day nine' in production.
Access is a scheduling risk
Several vendors gate API access behind a developer programme and an agreement, with timelines that vary, so apply early and plan the roadmap around the wait.
Methodology
Why each platform is priced separately
The low end of the range is arithmetic: the published $3,500 per platform multiplied by how many you selected. The upper end applies a scope multiplier for two-way sync or near-real-time delivery with historical backfill, shown as a percentage because “add webhooks” has no fixed dollar price.
Integrations do not get cheaper in bulk, so the calculator models no volume discount. Auth models, permission semantics, data shapes, background delivery and duplicate handling all differ per platform.
The per-platform notes reflect each vendor’s documentation as of September 2026. The behaviours are stable enough to plan around, but these APIs move, so re-check them before a roadmap commits to one.
Integrate one platform first, chosen by what your users wear instead of a matrix of everything competitors support. Most products need one done well long before they need six done badly, and a second integration is far easier to justify once the first is producing data somebody looks at.
FAQ
Wearable integration cost questions
How much does a wearable integration cost?
Zee Palm's published price is $3,500 per platform (HealthKit, Health Connect, Garmin, Whoop, Fitbit or Oura), covering design, implementation, edge-case handling, QA on real devices and documentation. Two-way sync or near-real-time delivery with historical backfill adds scope on top, which the calculator shows as a percentage.
Why is each platform priced separately instead of as one job?
Because they are separate projects. They differ in auth model, permission semantics, data shapes, background delivery, rate limits and how they handle duplicates. The work does not meaningfully compound: doing HealthKit does not make Whoop cheaper, because almost nothing transfers except your own internal data model.
What is the most common surprise in a wearable build?
Duplicate and missing data, not the API call. Health Connect's aggregate API deduplicates only Activity and Sleep. Every other data type is summed across all writing apps with no deduplication, which is the mechanism behind double-counted steps and silently doubled nutrition or glucose totals. On the Apple side, HealthKit cannot report that a read permission was denied at all: denied reads simply look like no data, so your product has to be designed for permanent uncertainty about whether a metric exists.
Should I use an aggregator like Terra instead of direct integrations?
For two or three platforms, a direct build usually wins on total cost, because you pay once rather than per user forever. Past five or six, an aggregator often wins on time to market. You trade a one-off build cost for an ongoing per-user fee and a dependency you do not control, and you inherit the aggregator's coverage claims instead of verifying each platform yourself. Device-coverage counts in aggregator marketing are claims, not audited figures.
Do I need the physical devices to build this?
Yes, and estimates often leave it out. Real-device QA is the only way to catch background-delivery behaviour, permission edge cases and duplicate handling, none of which reproduce reliably in a simulator. Budget for the hardware for every platform you support.
Next steps
Go deeper on the data layer
Work with us
Tell us which wearables your users have
Send the platforms and the data you need from each. We'll reply with scope, sequence and a fixed price, and flag any platform that can't give you the metric you're planning on.