HealthPipe

How it works

Set it up once. Then forget it.

Three things to decide, all on one screen.

Pick your data

Choose daily health metrics or workouts. Steps, heart rate, sleep and more.

Point it at a URL

Add your endpoint and any headers you need. Secrets stay in your iPhone's Keychain.

Set the rhythm

Run every few hours, daily or weekly. HealthPipe re-sends recent days so nothing is missed.

Features

Know it worked. At a glance.

Three times, one answer.

Is it Health, the export or iOS?

Last received from Apple Health
Data through: the newest data your server has
Last push, with its status and data-point count

An export's detail screen with the Latest card and a 28-day run calendar.

Days delivered.

Not just when it ran. What reached your server.

Runs tab: see every run, missed ones and failed ones included
Days delivered tab: see which days of data actually landed on your server
A missed run doesn't matter if a later one delivered the data
Anything undelivered is one tap away from being sent

The Days delivered calendar: 28 of 28 days delivered to the server, with the most recent days marked as still open to updates.

Your schedule, your range.

Built for how iOS really runs things.

Run every 1–7 hours, days or weeks
Choose how many days each run sends
Missed runs are logged, never hidden

No reminders to open the app.

Use your iPhone as usual. HealthPipe runs along with it.

Exports run in the background as you use your phone, with no notifications nagging you
Run every few hours, daily or weekly, and each run re-sends recent days
If iOS skips a run, it's logged and the next run catches up

Export format

One clean JSON payload.

Each run sends a single HTTP POST with a JSON body. The structure matches Health Auto Export, so existing receivers keep working.

♥

Health metrics

Daily totals and readings, one point per day: steps, energy, heart rate, HRV, sleep and more. Sleep includes stages and bed times.

↗

Workouts

Every workout with its start, end, duration, distance, energy and heart rate.

One export sends one kind of data. Add a second export for the other. CSV and GPX aren't supported.

POST https://your-server.com/health
Content-Type: application/json

{
  "data": {
    "metrics": [{
      "name": "step_count",
      "units": "count",
      "data": [{
        "date": "2026-09-18 00:00:00 -0300",
        "qty": 8412
      }]
    }]
  }
}

Privacy

Private by design.

There is no HealthPipe server in the middle. Your data goes from your iPhone to the URL you chose, and nowhere else.

No account, no sign-up

Install it and set up an export. There is nothing to register.

Read-only access

HealthPipe only reads from Apple Health. It never writes to it.

No ads, no tracking

No analytics SDKs and no third parties. Headers are kept in the Keychain.

FAQ

Good questions.

What do I need on the other end?

Any HTTPS URL that accepts a JSON POST. HTTP is allowed on your local network. Data is sent in the Health Auto Export JSON format.

Does it run in the background?

Yes, when iOS allows it. iOS decides when background work happens, so exact times aren't guaranteed. HealthPipe logs every missed run and re-sends recent days on the next one.

Can it read Health while my phone is locked?

No. iOS makes Health unavailable while the phone is locked, so a run in that moment is skipped and logged. The next run picks it up.

Which data can I send?

Daily health metrics such as activity, heart, respiratory, body and sleep, or workouts. One export sends one kind.

Where does my data go?

Only to the endpoint you enter. HealthPipe has no server of its own.

Your health data, sent where you want it.