HealthAPI

HealthAPI turns the data locked inside Apple Health into a hosted REST API. You install the iPhone app, grant it access to Apple Health, and it hands you an API key. From then on your steps, heart rate, sleep, workouts and history are reachable from any HTTP client, which means a script, a dashboard, or an AI assistant like ChatGPT or Claude can answer questions about your health without you exporting a file first.

The problem is that Apple Health is a rich store with no door for outside software. The data lives on the phone, and anything that wants to reason over your history has to be an iOS app itself or work from a manual export. If you've ever wanted to ask an assistant how your sleep compared across two months, or plot your resting heart rate against training load, the extraction step is the part that kills the idea.

The mechanics are straightforward. The app syncs your Apple Health data to the service, and the API serves pre-aggregated summaries so you're not reconstructing days from raw samples. Endpoints cover a daily summary of activity, energy, sleep and workouts, a weekly summary across ISO calendar weeks, per-day trends over anything from one to 365 days, workouts with type, duration, distance and energy, the latest reading for each metric, and raw samples with filters when you do want the underlying points. Metrics include steps, heart rate, heart rate variability, blood oxygen, respiratory rate, active and basal energy, distance, flights climbed, exercise time, sleep and workouts. Authentication is a bearer token, and keys can be rotated from the console.

Endpoints come in two families. The query endpoints are shaped for questions, a daily summary of steps, heart rate and workouts for a single day, and trends that return per-day statistics over a chosen window. The health endpoints are the fuller rollups and the raw material, complete daily and weekly summaries, workouts, samples and the latest reading per metric. A usage endpoint reports your plan tier and how much of the day's quota you've used, which is handy when an assistant is making calls on your behalf and you can't see them.

It's for people who want programmatic access to their own health data, whether that's a developer building a personal dashboard or someone wiring an assistant up to answer questions. The site frames it explicitly as a way for AI agents to work with health history, and the pre-aggregated daily and weekly endpoints are shaped for that kind of question and answer use rather than for bulk analytics. The obvious use is a conversational one. Connect the API to an assistant and ask how last week's sleep compared to the week before, or whether your resting heart rate has drifted since you started running. Because the summaries are already aggregated, the answers come from a handful of calls rather than thousands of samples, which matters when you're on a 100 request a day plan.

What sets it apart is that it's a hosted service rather than a library. There's nothing to run, no server to maintain, and the aggregation is done for you. It also takes data handling seriously in a visible way. There's a GDPR export endpoint that returns your account and health data as JSON, and an account deletion endpoint with a 30 day recovery window. The site is clear that HealthAPI is not a medical device and offers no medical advice.

Getting started takes a few minutes. Install the app from the App Store, sign in, grant it access to the Apple Health categories you want to share, and copy the key it issues. The console on the site shows usage and lets you regenerate the key, and the docs include a quickstart, an API reference and a rate limits page. Everything is served under a versioned API path.

The limits are real. It's Apple Health only, so Android and Google Fit users are out. Rate limits are modest, 100 requests a day on Pro and 1,000 a day on Developer, resetting at midnight UTC, and exceeding them returns a 429. App uploads don't count against the quota. The service is also a younger product with a small footprint, so anyone building something they'll depend on daily should read the docs and privacy policy carefully first.

Access is paid, with a seven day free trial that runs at the Pro limit of 100 requests a day. Pro is $4.99 a month and Developer is $9.99 a month for 1,000 requests a day, with an annual discount available in the app. There's no permanent free tier. The console, API reference, quickstart and rate limit pages are on the site, and questions go through the contact form.