Support

HealthPipe Support

Your health data, in motion. HealthPipe helps you export selected Apple Health data to your own HTTPS destination in JSON or CSV.

Get started

1. Open HealthPipe and follow the onboarding steps. Allow read access to the health categories you want to export.

2. Enter your HTTPS receiver URL. Add any headers your receiver requires, such as an authorization header. You need a destination that accepts HTTP export requests; a normal website address is not necessarily a receiver.

3. Choose your metrics, export format, date range, and grouping.

4. Use Sync Now to test a delivery, then check the delivery history and confirm that your receiver received the export.

5. Enable automatic exports and choose your preferred cadence. You can also enable workout-triggered exports and delivery alerts.

Automatic exports and iOS

HealthPipe uses iOS background capabilities and silent pushes to help run automatic exports. iOS decides when the app can run, so your chosen cadence is a preference, not a guaranteed delivery time. Opening HealthPipe gives it another opportunity to catch up. Force-quitting the app, limited connectivity, power restrictions, or a locked device can delay background work or access to health data.

Missing or incomplete data

Check that the data exists in Apple Health, that HealthPipe has read permission for the selected categories, and that your chosen date range includes it. Apple Health does not tell apps whether a read permission was denied; a category may appear empty. Revisit HealthPipe’s permissions in Apple Health or iOS Settings, then try Sync Now.

Exports contain selected metrics summarized according to your grouping settings. They are not a complete backup of every Apple Health record. Rolling date ranges overlap across deliveries, so your receiver should replace or deduplicate matching periods rather than blindly adding every export.

A delivery failed

Check your internet connection, receiver URL, required headers, and the outcome in delivery history. An HTTP 401 or 403 usually means the receiver rejected authorization. A server error or timeout usually requires checking your receiver or trying again later. A successful HTTP response confirms the receiver accepted the request; check the receiver itself to confirm how it stored the data.

Manage access and exports

You can change selected metrics and your destination in HealthPipe, turn off automatic exports, or revoke HealthPipe’s read access through Apple Health’s app permissions. HealthPipe reads health data and does not write changes back to Apple Health.

Contact

Email taylorarronj@gmail.com for help, bug reports, or privacy requests. Include your HealthPipe version, iOS version, device model, and a short description of what happened.

Please do not email health exports, passwords, API keys, authorization headers, or other sensitive information. Redact these from screenshots and error messages.

HealthPipe is a data export utility. It does not provide medical advice, diagnosis, or treatment.

Read the HealthPipe Privacy Policy