FIELD GUIDE · CONNECTING A SOURCE · № 09

healthLamprocapnos salutis

Connect Apple Health

Nothing can read Apple Health from off your phone, so this source inverts: the Console mints a private ingest endpoint and a secret, and your iPhone pushes your metrics to it on a schedule — through the Health Auto Export app, the path that runs in production. Postern keeps what your phone chooses to send, from the day it starts sending.

Health Auto Export on your iPhone · about 10 minutes · push, not pull

1

Mint the ingest endpoint in the Console

Console → Add a source → Apple Health → Create your ingest endpoint. The card renders two credentials: the ingest path — /api/ingest/<connection-id> — and the device secret, shown once. The path is not the full URL: Postern is never told your remote-access host, so you compose the URL yourself — the address tailscale serve gave the ingest port, plus the path, as in the box below. Copy the full URL and the secret; steps 3 and 4 paste them into your phone.

https://your-mac.tailnet.ts.net:8443/api/ingest/<connection-id>
The Console’s Apple Health connect card: Create your ingest endpoint — the path and its one-time device secret are minted here.

2

Install Health Auto Export on the iPhone

From the App Store. Its REST-API automations may require the app's paid tier.

App Store → Health Auto Export

3

Automation one — health metrics

Health Auto Export → Automations → new. These are the production gateway's own settings, copied from its running automation — set every field exactly. For the metric selection: production selects essentially the full list; start with everything and prune later, since each day's file is small.

Export Data Type Health MetricsDestination REST APIURL the full URL you composed in step 1Headers Authorization: Bearer <your secret> (the connect card's X-PCI-Webhook-Secret: <your secret> also works)Export Format JSON · Export Version v2Export File Length day · Batch Requests OFFExport Aggregation Default · Export Period DefaultAggregate Data ON · Aggregate Sleep ONInclude cycle tracking ON · medications ON · ECG OFF · heart-rate notifications OFF · state of mind OFF · symptoms OFF

4

Automation two — workouts

A second automation, identical in every field above, with three changes: Export Data Type is Workouts, Include Workout Metadata is ON, and Include Routes is ON (Include Health Metrics is OFF — the metrics automation already carries them). Two automations split by data type keeps each payload small and each failure legible.

5

Run one manually, watch the first rows land

Set each automation's schedule — production pushes every hour (sync cadence: 1 hour), and hourly is a good default — then run one by hand and watch the connection's first samples arrive in the Console. From then on your phone pushes on its own cadence — sleep, workouts, and every metric you selected, queryable by any agent you have granted health.

WHAT STANDS WHEN YOU FINISH

A health connection fed by your own phone, on your own schedule, with no cloud in between. The ingest endpoint accepts nothing without its secret, and the connection reports an honest freshness state — an agent asking about your sleep can see exactly how current the answer is.