How can I export Apple Health data?

Choose a snapshot file, an on-device automation or ongoing delivery to software you run.

Checked on 2026-11-07.

How do I export from the Health app itself?

Open the Health app on your iPhone, tap your profile, then Export All Health Data. Share the resulting export.zip, which contains export.xml. This is a snapshot; export again for later records. Your receiving software needs to parse Apple's XML.

Can I use Shortcuts?

Shortcuts' Find Health Samples actions can select Health records for an on-device workflow, with Health permissions. You maintain the shortcut and its output steps on the iPhone. See Apple Health API options for the route comparison.

How do I export a file from Syncky Health?

In Syncky Health, open Settings → Export a file. Choose Syncky JSON (native), Health Auto Export-style JSON (hae) or CSV (csv) and share to Files or AirDrop. InfluxDB line protocol is not a file-export format.

The direct-server and file pickers default to two calendar years and allow an earlier From without an app history-depth floor. Exporting to a local file is always free, for any period. Sending history to a direct server: Free during launch; plans are coming later. See launch access and pricing. Agent replay and incremental sync keep their history-window limits. Full history never goes through relay or agents.

Files are built one calendar day at a time and shared only when complete. Keep the app in the foreground: leaving it cancels local export. Failure or cancellation discards the working output; Retry recreates the whole original period. Native files can include daily quantity summaries for older history; HAE and CSV keep quantities raw. Local files contain no device/delivery metadata or deletions. See local file semantics.

Can I receive CSV or JSON continuously?

Configure an Apple Health webhook to send selected data directly to your own server as CSV or JSON. Your server receives plaintext; use HTTPS. Nothing passes through Syncky's servers on this route. The server contract defines formats, authentication, signing and replies.

iOS decides background opportunities, with no fixed interval, and Health reads require an unlocked iPhone. Delivery is at least once, so receivers must deduplicate. The app applies supported commands from a successful data reply only when Accept writes to Health is on for the server and the iPhone has the Sync plan. Writes apply at the next sync for the types the owner allowed for writing in the app, with iOS Health permission. See writing to Apple Health.

Apple Health to CSV

Syncky's CSV column layout is:

type,uuid,start,end,value,unit,value_name,source,device,user_entered

CSV follows RFC 4180 with CRLF line ends; times use RFC 3339 in the sample's known time zone, otherwise UTC. For formula-character protection, source and device fields starting with =, +, -, @, a tab or a CR receive a leading apostrophe. Webhook deletion rows contain only type, uuid and value_name=deleted; local export files have no deletions.

State of mind, assessments, audiograms, activity summaries, routes and heartbeat series are not sent in CSV. See the CSV contract for escaping and row meanings.

What about other export apps and AI connectors?

Other categories include automation/export apps for files or server delivery, and AI connectors for querying an export, a local service or a hosted copy. Check the destination, permissions and delivery limits of the tool you choose. The Apple Health MCP comparison lists named projects with dated primary sources.

With Syncky's agent route, Relay sees delivery metadata and no health values; hub notices are plaintext. Sealed envelopes wait until acknowledgment or expiry, at most 7 days. Your agent receives plaintext, and a chosen model sees what the agent supplies.