For the last year our iOS app, MetricBridge, has read Apple Health on the phone and exported it wherever the user points it: iCloud Drive, a folder, their LAN, or a webhook. The webhook is the part nobody asks about, and it is the part that became its own product.
If you run a wellness or coaching platform and you want a user's Apple Health data today, the usual move is a cloud health-data API. Terra, Junction, Sahha, ROOK, Spike, Thryve. Entry tiers run $299 to $499 a month, then per-user charges after a cap. The data leaves the phone, lands on the vendor's server, gets forwarded to yours. That vendor is a processor in the chain, and you inherit the whole conversation: DPAs, sub-processors, the security review that asks why a third party sees your users' health data at all.
We already had the hard half built. 190 Apple Health metrics, read on device, read-only. A signed webhook, Standard Webhooks v1, that POSTs a JSON payload to any HTTPS endpoint the user chooses. Published JSON Schema 2020-12 and an OpenAPI 3.1 spec. A reference receiver you can run locally. A zero-dependency Node kit with a 15-rule conformance suite you point at your own endpoint before you go near a real user.
So the platform side of that webhook became a product: MetricBridge for platforms.
Three things make it a different offer from the cloud APIs.
We are not in the data path. The payload goes from the user's phone straight to your endpoint. We never hold it, never see it, never store it. Your privacy policy gets shorter, not longer, because there is no new processor to name.
Flat pricing. $1,800 a year for a Certified Partner listing and a versioned conformance report. $3,600 for Partner Plus with co-marketing, quarterly reviews and 1-business-day support. A $2,500 fixed 60-day pilot, fully credited to year one. No per-user price, no per-record price. A fee that scales with health data is a different legal animal, and we did not want to be it.
No SDK in your app. You give the user a webhook URL and a token. The app on their phone does the rest. Your client code does not change.
The integration guide, the verification steps (raw HMAC in both Node and Python), the storage rules that keep you out of processor territory, and the conformance kit are all public. You can read every one of them before you decide anything.
If you are building a platform and you have been putting the Apple Health integration off because the pricing never made sense, the offer is here: https://dub.sh/RZ1LsfT
Or email us, there is a link on that page.
Top comments (0)