MyFitnessPal API in 2026: Is It Open? How to Integrate
CTO & Co-Founder
CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

You cannot get MyFitnessPal data from the MyFitnessPal API today. The MyFitnessPal API page says "We are not accepting requests for API access at this time." The working route is the phone: the user turns on sharing from MyFitnessPal to Apple Health on iPhone or Health Connect on Android, and your app reads the food, water and weight entries from there. We found no MyFitnessPal fee for that route. It does need your own mobile app, and you only get what MyFitnessPal chooses to write. If your product is web-only, you cannot use MyFitnessPal data today.
Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery.
MyFitnessPal integration at a glance
| Question | Short answer |
|---|---|
| Is there an official API? | It exists, but it is closed to new requests. The only contact offered is a licensing email, partners@myfitnesspal.com. |
| Cost to the developer | API: not published. Phone route: no MyFitnessPal fee found. |
| Does the end user need anything paid? | A MyFitnessPal account. Whether sharing to Apple Health or Health Connect needs MyFitnessPal Premium is not published. |
| Same-day start? | Likely, on the phone route, if you already have a mobile app. No MyFitnessPal sign-up is needed. Our estimate, not a vendor statement. |
| Who approves scale-up? | Not MyFitnessPal on the phone route. Apple reviews your iOS app. Google reviews your Health Connect permission declaration on Play. |
| HIPAA and BAA | Not published by MyFitnessPal. On the phone route, the data reaches your app from the user's phone, so your own HIPAA program applies. |
| Raw or summary data? | Per meal entries on the phone route, as reported by third parties. Exact fields not published by MyFitnessPal. |
| First build | 3 to 5 weeks for an iOS and Android reader with background upload and FHIR mapping. Our estimate. |
Integration strategies
| Route | Own mobile app? | Own server? | Vendor approval or contract? | SDK? | Latency | Supported data | Not supported | Best for |
|---|---|---|---|---|---|---|---|---|
| Cloud REST API | n/a | n/a | Closed. "Not accepting requests for API access." | n/a | n/a | The page only says "RESTful interfaces". No public field list. | Everything, for new developers. | No one today. |
| Partner or licensing deal | Unknown | Likely | Yes. Email partners@myfitnesspal.com. Whether this leads to API access is not published. | Unknown | Unknown | Unknown | Unknown | Large programs with a business case for MyFitnessPal. |
| Webhooks or push | n/a | n/a | Not published | n/a | n/a | None found | All | n/a |
| MyFitnessPal phone SDK | n/a | n/a | None found | None found | n/a | n/a | n/a | n/a |
| Apple Health (HealthKit) | Yes, iOS | Yes, to receive uploads | No MyFitnessPal approval. Apple App Review. | HealthKit | When the user's phone syncs and your app runs | Food as meal summaries with most nutrients, and weight (both ways). It reads exercise and sleep. | Caffeine, vitamin A and meal timestamps. Food logged before the user connected. | iPhone users in any program |
| Health Connect (Android) | Yes, Android | Yes | No MyFitnessPal approval. Google Play health permission declaration. | Health Connect | When the phone syncs | Food as meal summaries, and water | Exercise MyFitnessPal received from Garmin or Polar. Users cannot link Google Health and Health Connect at the same time. | Android users |
| Aggregators, checked 10 November 2026 | Terra lists MyFitnessPal as a cloud source. Junction lists it but marks it deprecated. Validic lists it as restricted and not taking new applications. Spike lists it with no route stated. ROOK does not list it. Thryve and Sahha coverage is not published. | |||||||
| File export | No | Yes, to parse | Not published | No | Manual | Not published in vendor docs | Ongoing sync | One-off imports only |
For a healthcare program such as diabetes, obesity or GLP-1 support, build one phone reader for Apple Health and Health Connect and treat MyFitnessPal as one of several food apps that feed it. For a wellness or coaching app, the same reader works, and it also picks up nutrition from other food loggers. Email the licensing contact only if MyFitnessPal itself is the core of your offer.
Build it yourself, use an aggregator, or work with a partner
| Question | Build in-house | Wearable aggregator | Build with a partner (Nirmitee) |
|---|---|---|---|
| Whose app reads the data? | Yours, on iOS and Android | The aggregator's phone SDK inside your app, where it lists MyFitnessPal at all | Yours. We build the reader in your app. |
| MyFitnessPal approval | None on the phone route. The API is closed. | None on the phone route | None on the phone route |
| Coverage today | Whatever MyFitnessPal writes to Apple Health and Health Connect | Mixed. Terra lists it, Junction marks it deprecated, Validic lists it as restricted (checked 10 November 2026). | Same as in-house |
| Background reads and sync | You build them | The SDK runs them | We build them, then hand them to you or run them |
| Data model | Health Connect and HealthKit types | The aggregator's schema | FHIR Observations for your EHR or remote monitoring stack |
| Other food apps and devices later | The same reader picks up any app that writes to the health store | Many sources through one API | Same reader reused across apps and devices |
| Time to first real user | Depends on your team | Depends on the aggregator's onboarding | 3 to 5 weeks of build in our estimate, plus Apple and Google review |
| Cost shape | Engineering time | Aggregator fee. Pricing is not published. | Project fee, scoped after a call |
What data you can get
Everything below comes through Apple Health or Health Connect. MyFitnessPal does not publish the exact data types it writes. The rows come from third-party guides and help pages, so test each one on a real phone.
| Data type | Granularity | History window | Push or pull |
|---|---|---|---|
| Energy intake (calories) | Per meal entry | Depends on what has synced to the phone. Not published. | Pull from the phone store |
| Macronutrients (carbohydrate, protein, fat) | Per meal entry | Not published | Pull |
| Meal grouping | Default meal names only on Health Connect | Not published | Pull |
| Water | Per entry. One-way from MyFitnessPal on Health Connect. | Not published | Pull |
| Body weight | Per entry | Not published | Pull |
| Exercise logged in MyFitnessPal | Per session | Not published | Pull |
| Micronutrients (fiber, sugar, sodium and others) | Not published | Not published | Pull, if written |
All of this lives on the phone. Your server only sees new data when your app uploads it.
What is inside one nutrition record
MyFitnessPal does not say which fields it fills. What it can fill is set by the platform. On Android, Google's NutritionRecord defines the fields below.
| Field | What it holds |
|---|---|
| startTime, endTime | Required. A nutrition record covers a time interval, not a single moment. |
| mealType | One of five values: unknown, breakfast, lunch, dinner or snack. This is why custom meal names cannot reach Health Connect. |
| name | Optional food or drink name. Whether MyFitnessPal fills it is not published. |
| energy, totalCarbohydrate, protein, totalFat | Optional. Energy in calories, the rest as mass. |
| Fiber, sugar, sodium, caffeine, vitamins and minerals | Optional fields, each with a valid range in grams |
| metadata.dataOrigin | The app that wrote the record. Filter on it to keep only MyFitnessPal entries. |
Water is a separate HydrationRecord with a volume over a time interval. On iPhone, Apple groups nutrition samples, such as dietary energy consumed, into a single food correlation object.
What you cannot get
- Any server-to-server feed. The API is closed to new requests.
- Food names, brands, barcodes, recipes or the food database. No source we read says these reach Apple Health or Health Connect.
- Custom meal names on Health Connect. Only default meal names sync.
- Exercise that MyFitnessPal itself received from Garmin or Polar, on Health Connect.
- Goals, diary notes, community posts or premium plan content. Not documented on any route.
- Data from users who do not install your app.
- Webhooks. None found.
How to get access
- Read the MyFitnessPal API page. It states that API requests are not accepted. No approval path exists today.
- If MyFitnessPal is central to your offer, email partners@myfitnesspal.com. Who decides and how long it takes: not published.
- For the phone route, add HealthKit to your iOS app and ask for read access to dietary energy, macros, water, weight and workouts. Apple reviews your app.
- On Android, add Health Connect and declare the permissions. Google Play reviews the health permission declaration. Timing set by Google, not published by MyFitnessPal.
- Tell users how to turn on sharing. On iPhone they allow MyFitnessPal to write to Health. On Android they connect Health Connect from Apps and Devices in MyFitnessPal.
- Test on real phones with a real food diary before launch.
From zero to your first MyFitnessPal data in four steps
There is no MyFitnessPal API key to get. These steps read MyFitnessPal entries from Health Connect on Android. The iPhone path is the same shape with HealthKit.
- Declare the permissions. Add android.permission.health.READ_NUTRITION and READ_HYDRATION to your manifest. Add READ_HEALTH_DATA_IN_BACKGROUND if you want reads while your app is closed.
- Have the user turn on sharing. They connect Health Connect from Apps and Devices in MyFitnessPal, then grant your app read access in the Health Connect prompt.
- Read the records. This is Google's documented read call with the nutrition type. Results come in pages of 1,000 by default, so follow the page token.
val response = healthConnectClient.readRecords( ReadRecordsRequest( NutritionRecord::class, timeRangeFilter = TimeRangeFilter.between(startTime, endTime) ) ) response.records.forEach { record -> /* keep MyFitnessPal entries, upload */ } - Load history once, then sync changes. Health Connect lets you read 30 days before the first permission grant unless you also ask for PERMISSION_READ_HEALTH_DATA_HISTORY. After the first load, use a Changes token to pick up edits and deletions. An unused token expires within 30 days, so keep a time-based fallback.
Terms you must know
No MyFitnessPal API terms are on offer to sign, since the API is closed. We found no published MyFitnessPal clauses on the topics below, so there are no section numbers to cite. On the phone route you do not agree to MyFitnessPal terms. You agree to Apple's and Google's rules for health data, and to your own privacy policy and consent screen.
- Medical use: not published by MyFitnessPal for any data route. For a healthcare product, treat food logs as patient-reported data and say so in clinical screens. For a wellness app, no extra limit found.
- PHI, HIPAA and BAA: not published. Once a food log reaches your server with patient identity, it is your PHI under your HIPAA program. No MyFitnessPal BAA is needed on the phone route, because MyFitnessPal does not send you anything.
- Storage and retention: no MyFitnessPal rule applies on the phone route. Apple and Google platform rules and your own retention policy apply.
- AI training: no MyFitnessPal clause found. Check Apple's and Google's health data rules before you train a model on user data.
- Branding: not published. Do not imply a partnership with MyFitnessPal.
- Data selling: not published by MyFitnessPal. Check Apple's and Google's health data rules before any resale or sharing plan.
- Termination: on the phone route, MyFitnessPal can stop writing to Apple Health or Health Connect at any time, and the user can turn sharing off.
- Competing products: not published.
Cost and payment terms
- API fees: not published. API closed.
- Licensing deal: not published.
- Phone route: no MyFitnessPal fee found.
- End-user subscription: whether Apple Health or Health Connect sharing needs MyFitnessPal Premium is not published.
- Aggregator fees: not published in the sources we read.
Use cases
1. Diabetes program meal review
The patient logs meals in MyFitnessPal and turns on sharing to Apple Health or Health Connect. Your patient app reads new nutrition entries in the background and uploads them. Your server writes carbohydrate and energy intake as FHIR Observations, and the care team sees daily carbs next to glucose readings from a separate device route. Data used: carbohydrate, energy intake, meal grouping.
- The patient never opens your app, so nothing uploads. Fix: background delivery on iOS, scheduled reads on Android, and a reminder if no data arrives for two days.
- The patient logs meals late, after midnight. Fix: key observations to the entry time, and update past days when late entries arrive.
- Carbs shown as a clinical fact. Fix: label them "patient-logged" in the EHR view.
2. GLP-1 support and weight program
The member shares nutrition and weight. Your app reads weekly intake and weight entries and shows the member their trend. The coach sees a weekly summary in your coaching console. Data used: energy intake, protein, body weight.
- Weight comes from both a smart scale and MyFitnessPal. Fix: keep the source on each reading and prefer the scale.
- Protein missing for some foods. Fix: show "not logged", never zero.
3. Dietitian-led chronic care
The dietitian asks the patient to log for two weeks. Your app collects the entries, and the dietitian reviews daily totals by meal before the visit. Data used: calories, macros by meal, water.
- Custom meal names do not sync on Health Connect, so entries land under default meals. Fix: tell patients to use default meals.
- Food names are not available. Fix: ask the patient to bring a screenshot of the diary for detail.
4. Wellness coaching app
The user links Apple Health or Health Connect once. Your app shows calories in against active energy from their watch. Data used: energy intake, water, exercise.
- Exercise counted twice, once from the watch and once from MyFitnessPal. Fix: dedupe by time window and source.
- Cardio from other apps only syncs into MyFitnessPal before midnight with duration and calories. Fix: read exercise straight from the health store, not via MyFitnessPal.
5. Payer wellness challenge
Members earn points for logging food on a set number of days. Your app counts days with any nutrition entry. Data used: presence of nutrition entries.
- Members who never open the phone app may have nothing in the phone store. Fix: count only days that reached the health store, and tell members that up front.
- Points disputes. Fix: store the entry timestamp and source for each counted day.
MyFitnessPal data in an EHR or remote monitoring program
Most care teams want food logs next to glucose, weight and visit notes, not in a separate app. The usual pattern is to turn each entry into a FHIR Observation, the standard record for a measurement, and send it to the EHR or the remote monitoring platform. Mark each one as patient-reported, since a person typed it in.
| MyFitnessPal value (via the health store) | FHIR Observation | Code |
|---|---|---|
| Energy (calories) per meal | Calorie intake total | LOINC 9052-2 |
| Carbohydrate per meal | Carbohydrate intake, estimated | LOINC 9059-7 |
| Protein per meal | Protein intake, estimated | LOINC 9079-5 |
| Fat per meal | Fat intake, estimated | LOINC 9066-2 |
| Water per entry | Fluid intake, estimated | LOINC 8984-7. Use 9108-2 only for a 24-hour total. |
| Body weight | Body weight | LOINC 29463-7 |
Keep the Health Connect record id or the HealthKit sample id on each Observation, so an edit or deletion found in the next sync can update it.
Known blockers and gotchas
- API closed. No new API access. Do not plan a server integration with MyFitnessPal. Build the phone route.
- Your own app is required. HealthKit and Health Connect are read on the phone. A web-only product cannot read them.
- Undocumented fields. MyFitnessPal does not publish what it writes to Apple Health. Test with a real diary and record what you see.
- Custom meal names drop on Android. Only default meal names sync to Health Connect, per third-party help pages.
- Water is one-way on Android. MyFitnessPal writes water to Health Connect but does not read it back.
- Midnight cutoff for exercise. Cardio from other apps syncs into MyFitnessPal only with duration and calories and before midnight, per third-party help pages.
- Garmin and Polar exercise does not flow on to Health Connect through MyFitnessPal. Read those devices directly.
- Google Play review. Health Connect permissions need a declaration and Google review. Leave time for it.
- Aggregator claims. Sahha and Thryve advertise MyFitnessPal through the phone routes. We did not verify this. Ask for a test account.
Delivery timeline
Our estimate for a first build of the phone route, not a measured figure.
| Week | Work | Depends on vendor? |
|---|---|---|
| 1 | HealthKit reader for nutrition, water, weight and workouts. Test with a real MyFitnessPal diary. | No |
| 2 | Health Connect reader, permission declaration | Google Play review (Google, not MyFitnessPal) |
| 3 | Background upload, retry, dedupe, server API | No |
| 4 | FHIR Observation mapping, clinical or coaching screens | No |
| 5 | App Store and Play release | Apple and Google review |
Questions to ask MyFitnessPal before you sign
- Is there any route to API or data partnership for a healthcare program today, and who decides?
- Exactly which data types does MyFitnessPal write to Apple Health and Health Connect, and with what granularity?
- Does sharing to Apple Health or Health Connect need a Premium subscription?
- Do food names or micronutrients reach either health platform?
- Does MyFitnessPal object to a healthcare product reading its entries from the health platforms?
- Will MyFitnessPal give notice before it changes what it writes?
Other device integration guides
MyFitnessPal is often one source among several. Each guide below uses the same layout, so you can compare access, data and terms side by side. For the full service, see medical device integration.
- Oura API integration guide
- WHOOP API integration guide
- Garmin API integration guide
- Ultrahuman API integration guide
- Eight Sleep API integration guide
- Fitbit and Google Health API integration guide
- Apple Health API integration guide
- Health Connect API integration guide
- Samsung Health API integration guide
- Withings API integration guide
- Dexcom API integration guide
- FreeStyle Libre API integration guide
- Polar API integration guide
- COROS API integration guide
- Suunto API integration guide
- Strava API integration guide
- Peloton API integration guide
Ready to build your MyFitnessPal integration?
Tell us your device, your users and your target date, and we will send back the route, the vendor approvals you need and a build plan. Book a call about your device integration.
For whoever builds this
Auth and permissions
- No MyFitnessPal OAuth available. Direct API auth not published.
- iOS: HealthKit read authorization per data type, set by the user. Treat "no data" as possibly "no permission" and prompt the user to check.
- Android: Health Connect per-type read permissions, plus the Play Console health permission declaration.
Endpoints
- None from MyFitnessPal. Your own upload API receives batches from the phone.
Rate limits and webhooks
- Not published for MyFitnessPal. Not applicable on the phone route.
FHIR mapping
| Data | LOINC | Status |
|---|---|---|
| Energy intake | 9052-2 | Unverified, confirm against LOINC and your IG |
| Carbohydrate intake | 9059-7 | Unverified |
| Protein intake | 9079-5 | Checked 11 Nov 2026 |
| Fat intake | 9066-2 | Checked 11 Nov 2026 |
| Water or fluid intake | 9108-2 (fluid intake 24 hours) | Unverified, check the time period fits per-entry data |
| Body weight | 29463-7 | Unverified |
Tag every Observation with the source app and mark it as patient-reported.
Version notes
- No API version or sunset dates published. API page read November 10, 2026.
Sources
- MyFitnessPal Apple Health connection, https://support.myfitnesspal.com/hc/en-us/articles/360032271092-Apple-Health-connection-and-syncing, read 10 November 2026.
- MyFitnessPal Health Connect FAQ, https://support.myfitnesspal.com/hc/en-us/articles/10553948248973-Health-Connect-FAQ-and-Troubleshooting, read 10 November 2026.
- Terra supported integrations, https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations, read 10 November 2026.
- Junction providers list, https://docs.junction.com/wearables/providers/introduction, read 10 November 2026.
- Thryve data sources overview, https://docs.thryve.health/thryve-data-sources/overview, read 10 November 2026.
- ROOK data sources, https://docs.tryrook.io, read 10 November 2026.
- Sahha integrations, https://www.sahha.ai/docs/connect/integrations.md, read 10 November 2026.
- Spike integrations, https://www.spikeapi.com/integrations, read 10 November 2026.
- Validic supported devices and restricted vendor list, https://www.validic.com/features/supported-devices/, read 10 November 2026.
- MyFitnessPal API page, https://www.myfitnesspal.com/api (redirects to https://myfitnesspalapi.com/), read November 10, 2026
- MyFitnessPal Apple Health FAQ, https://support.myfitnesspal.com/hc/en-us/articles/360032271092-Apple-Health-FAQ-and-Troubleshooting, title only, page blocked automated reading on November 10, 2026
- Sonar Health guide (third party), https://www.sonarhealth.co/blog/sync-myfitnesspal-with-apple-health/, read November 10, 2026
- Sahha MyFitnessPal integration page (third party), https://sahha.ai/integrations/myfitnesspal/, read November 10, 2026
- Hevy help center (third party), https://help.hevyapp.com/hc/en-us/articles/34895971528727-How-to-Connect-to-MyFitnessPal-Apple-Health-Health-Connect, read November 10, 2026
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does MyFitnessPal have a public API?
How can my app get MyFitnessPal data without the API?
What MyFitnessPal data reaches Apple Health or Health Connect?
Do food names sync from MyFitnessPal to Apple Health?
Does a MyFitnessPal integration cost money?
Can I use MyFitnessPal data in a diabetes or GLP-1 program?
Will MyFitnessPal sign a BAA?
Can aggregators like Sahha or Thryve give me MyFitnessPal data?
How long does a MyFitnessPal integration take?
Why does some exercise not appear from MyFitnessPal on Android?
Can I get a MyFitnessPal API key?
Which Health Connect permissions do I need for MyFitnessPal data?
How much MyFitnessPal history can my app read on Android?
Is there a webhook when a user logs a meal?
Why does my iPhone app see no MyFitnessPal data?
What units does MyFitnessPal nutrition arrive in?


