If you are building something on Apple Health data and need it from more than one iPhone, this is how people do it with HealthSave. Each person installs the app, points it at your server, and their data goes from their phone to you. HealthSave is not in the middle. Background sync is a Pro feature, and you can pay for other people's Pro unlock from inside the app.
Who asks for this
- A company with its own ingest server that wants a few testers sending real data.
- A research group or a coach collecting the same metrics from a small group, with their consent.
- A family where one person runs the server and everyone else just needs the app to work.
How the seats work
- Open Settings > Gift HealthSave Pro (HealthSave 1.8.1 or later).
- Buy one gift per person. Each gift costs the same one-time price as Pro.
- The app gives you a link for each gift. Send it to the person it is for.
- They install HealthSave, tap the link, and claim it. Pro unlocks on their own Apple Account and stays with them.
Both of you need to be signed in to iCloud, because the gift travels through your iCloud and theirs. The first person to open a link gets that gift, so send each link to one person. The gift screen shows which gifts have been claimed.
Gifting is new. Buy one, send it, and check that it unlocks Pro before you buy the rest.
What this is not
Apple is the seller, so there are no invoices from us, no volume pricing, and no license keys to manage. In-app purchases can't be bought in bulk through Apple Business Manager, which is why gifting exists. A gift covers one person, not their Family Sharing group. Refunds go through Apple to the buyer, and a refunded gift stops unlocking Pro.
Pointing the app at your server
In Settings > Server Sync, each person enters your base URL and, if you use one, an API key. The app then posts batches to your endpoint in the background. What your server has to implement is written down:
- The HealthSave API contract: endpoints, authentication, batch format, retry and duplicate rules.
- Backends that speak HealthSave: the official hub, community servers, and advice from real deployments.
- Every exportable metric, with its exact identifier and unit.
If you would rather not write a server, HealthSave Observatory is the reference implementation and runs in Docker.
Whose data it is
The data belongs to the person wearing the watch. It goes from their phone to the server they typed in, and nowhere else. We never receive it and can't see it. Getting their consent, and looking after what arrives, is on you.
HealthSave is not a medical device. It is for informational purposes only and does not diagnose, treat, cure, or prevent any disease or condition.
Questions about the wire format
Write to support@healthsave.app. Proxy logs and the exact request that surprised you get the fastest answer.