Apple Health API: what works from a server?

There is no Apple Health web API. HealthKit is on the device. To use Apple Health data on a server, export it or let an iPhone app read the types the owner shares and deliver them to your destination.

Can I use the Health app's XML export?

The Health app's Export All Health Data produces an archive containing export.xml. Copy it to your computer or server and parse it there. It is a snapshot: getting later records requires another export. Exporting a file grants no ability to write entries back to Apple Health. The MCP comparison includes projects that read these exports.

Can Shortcuts move or log Health data?

Shortcuts can run an on-device workflow using Health actions. For a supported write type, Log Health Sample adds an entry with the owner's Health permission. A shortcut still runs on the iPhone; it is not a server-side Health endpoint. Choose this route for a workflow you maintain on the phone.

How can an iPhone app push to my endpoint?

An iPhone app can read HealthKit with the owner's permissions and send selected data to your HTTP endpoint. Syncky Health provides this direct route: configure your server in the app and choose the data to share. Your server receives plaintext. Nothing passes through Syncky's servers on this route; use HTTPS to protect data in transit.

The server contract defines Syncky JSON, Health Auto Export JSON, CSV and InfluxDB line protocol, authentication, signing and replies. Start with its receiver formats or the n8n and Home Assistant guides.

How can an agent receive data over MCP?

Pair Syncky Health with your own agent. The agent receives the selected data and exposes local MCP tools to a compatible client. Client health-data envelopes are encrypted end to end through Syncky Relay, with no public URL needed for your agent.

Relay sees delivery metadata and no health values, and emits plaintext hub notices. Sealed envelopes wait until acknowledgment or expiry, at most 7 days. The agent receives plaintext, and a chosen model sees what the agent supplies. Review the MCP approaches and named projects for other architectures.

What limits apply to delivery and writes?

iOS schedules background work, and Health reads require an unlocked iPhone. Syncky applies writes when the app runs and the phone is unlocked. Samples can be hours old; a queued command is not proof it was applied.

Syncky writes apply at the next sync for the types the owner allowed for writing in the app, with iOS Health permission. Check the phone's applied result for the command version. See writing to Apple Health from a server or agent for allowed types, refusal reasons and source metadata. A direct server waits for a data request before it can return write commands.