MyFitnessPal Native API · Live

Pull live MyFitnessPal data
in the time it takes
to read this sentence.

Food diary entries with full macro and micronutrient breakdowns, exercise logs, weight measurements, water tracking, and nutrition goals via the same JSON API the mobile app itself uses — structured and delivered as clean JSON or CSV.

See a Live Response
Personal account data your own diary, your own credentials
<3s avg. response time
99.9% uptime SLA
50M+ requests / month served
GET /v2/diary
LIVE
// streaming a live diary entry pull...
Trusted by developers and health-tech teams pulling MyFitnessPal data
MacroBridge Fitport NutriTrace HealthAI WellnessWorks DietScope
500+
GLOBAL CLIENTS SERVED
300+
PROJECTS DELIVERED
50M+
MONTHLY API CALLS
24/7
DEDICATED SUPPORT
Why Choose Our MyFitnessPal API

MyFitnessPal's official API is partner-only. We give you the same native data, self-serve.

MyFitnessPal restricts its official REST API to approved partners through an application process. Our infrastructure talks to the same native mobile API the MyFitnessPal Android app uses — login, food search, diary read/write/delete, weight measurements, exercise logs, nutrition goals, and water tracking — and packages it as a clean, self-serve integration.

01

Native mobile API, not web scraping

We call the same JSON REST v2 endpoints the official app uses, which returns richer structured data than scraping the website.

02

Full diary write access

Not just reading — our client supports logging, modifying, and deleting food entries, exercise entries, weight measurements, and water intake.

03

Complete nutrition breakdown

Every diary entry returns calories, protein, carbs, fat, fiber, sugar, sodium, and per-meal aggregation as computed by MyFitnessPal.

04

Built for personal data portability

Access your own diary programmatically without waiting for a Premium export email or relying on browser extensions.

MyFitnessPal API Features

Everything you need to keep MyFitnessPal data flowing.

⚡

Real-time diary extraction

Trigger an on-demand pull for any date and get a fresh response — not a stale cache.

🧩

Custom field selection

Request only the fields you need — macros, exercise, water — to cut payload size and parsing time.

🍎

Food search & logging

Search the MyFitnessPal food database and log entries programmatically with serving sizes and meal assignment.

🏋️

Exercise diary access

Read cardio and strength exercise logs with duration, calories burned, and per-exercise breakdown.

⚖️

Weight measurement tracking

Read and write weight measurements with automatic same-day upsert.

💧

Water intake tracking

Read and set daily water intake with both cup and milliliter units.

What Data Can You Access?

Every field your diary contains — meals, macros, exercise, and progress included.

DiaryFood entries by mealBreakfast, lunch, dinner, snacks with timestamps
DiaryFull nutrition breakdownCalories, protein, carbs, fat, fiber, sugar, sodium
DiaryMicronutrientsVitamins, minerals, and cholesterol per entry
DiaryServing size & quantityUnit, value, and nutrition multiplier per entry
ExerciseCardio & strength logsDuration, calories burned, exercise type
ExerciseSteps & daily burnStep counts and total calorie burn from trackers
MeasurementsWeight historyWeight entries with date and unit
MeasurementsBody measurementsNeck, waist, hip entries when logged
WaterDaily water intakeCups and milliliters per date
GoalsNutrition goalsDaily calorie and macro targets
GoalsNet calorie goalCalorie target adjusted for exercise burn
NotesFood & exercise notesCustom notes attached to diary entries
Supported MyFitnessPal Categories

Nutrition, exercise, measurements, and goals — one integration.

Switch the resource parameter to pull data from a specific diary vertical with the same consistent response shape.

🍎

Food Diary

Meal entries with full nutrition breakdown.

🏋️

Exercise Diary

Cardio and strength logs with calorie burn.

⚖️

Measurements

Weight and body measurement history.

🎯

Goals & Water

Nutrition targets and daily water intake.

ScopePersonalYour own account data, accessed with your credentials
ProtocolNative APISame endpoints the official mobile app uses
FreshnessReal-timeDiary and measurement data checked on every request
MyFitnessPal API Endpoints

A small set of endpoints that cover the whole diary lifecycle.

Method Endpoint Description Typical use
GET /v2/diary Food and exercise diary entries for a date Daily nutrition review
POST /v2/diary Log a food entry with serving size and meal Automated meal logging
GET /v2/search/nutrition Search the food database with macros Food lookup before logging
GET /v2/measurements Weight and body measurement history Progress tracking
POST /v2/measurements Log or update a weight measurement Automated weight logging
POST /v2/diary/water Set daily water intake total Hydration tracking
GET /v2/nutrient-goals Daily calorie and macro targets Goal monitoring
Live API Response Example

This is exactly what comes back. No extra parsing needed.


        
Popular MyFitnessPal API Use Cases

Built for developers who want programmatic access to their own nutrition data.

📊

Personal data export

Export your full diary history programmatically without waiting for a Premium CSV email.

🤖

MCP server integration

Connect MyFitnessPal to Claude and other LLM clients for conversational nutrition logging and analysis.

📈

Trend analysis

Track calories, macros, weight, and water over time with structured data.

🔄

Data portability

Move your nutrition history to other platforms like NutriTrace or Google Sheets.

🍽️

Automated meal logging

Build scripts that search, select, and log foods with the correct serving sizes.

📉

Weight tracking automation

Log weight from external scales or wearables directly into your MyFitnessPal diary.

🧪

Research & experimentation

Analyze your own nutrition patterns for personal health experiments.

📱

Custom app development

Build personal dashboards or companion apps that read and write to your diary.

How the MyFitnessPal API Works

From credentials to structured data in five steps.

1

Get your API key

Sign up and generate a key from your dashboard in under two minutes.

2

Provide credentials

Authenticate with your MyFitnessPal account via OAuth or session cookie.

3

Send the request

Call the endpoint with a date, food search query, or measurement value.

4

We handle the hard part

Session management, Cloudflare bypass, and parsing all happen behind the scenes.

5

Receive structured data

Get clean JSON or CSV back in seconds, ready to drop into your pipeline.

Developer-Friendly Integration

Built by people who read the docs too.

One consistent JSON schema across every resource and every endpoint. No SDK lock-in — plain REST calls work from any language or platform.

→

Predictable REST design

Standard HTTP verbs, query params, and status codes — nothing proprietary to learn.

→

JSON, CSV, or webhook delivery

Get results inline, as a downloadable file, or pushed to your endpoint when a batch job finishes.

→

Sandbox & test keys

Free sandbox environment with sample data so you can build before you connect your account.

→

Postman collection & SDK snippets

Import a ready-made collection or copy request snippets for Python, Node.js, and cURL.

Quickstart
API Performance & Reliability

Numbers we publish because we track them daily.

99.9%
Uptime SLA
<3s
Avg. response time
99.3%
Successful extraction rate
10K+
Concurrent requests supported
Security & Compliance

Personal health data needs clear boundaries — here's where ours sit.

🔐

Your credentials, your data

We never store your MyFitnessPal password in plaintext. Authentication tokens are encrypted at rest and can be revoked anytime from your dashboard.

📄

GDPR Article 20 alignment

MyFitnessPal data export supports your right to data portability. Our API gives you programmatic access to the same data the official export provides.

🔒

Encrypted in transit

All requests and responses travel over TLS 1.2+. API keys can be scoped and rotated anytime.

✓ISO 9001:2015 Certified ✓ISO/IEC 27001:2013 Certified ✓IAF Multilateral Recognition ✓GDPR-aligned workflows
API Documentation & Resources

Everything to go from key to production.

Guide

Quickstart Guide

Get your first API response back in under five minutes.

Read guide →
Reference

Full API Reference

Every endpoint, parameter, and response field documented in detail.

View reference →
Tool

Postman Collection

Import ready-made requests for every MyFitnessPal API endpoint.

Download →
Code

SDKs & Code Samples

Python, Node.js, PHP, and Ruby snippets for every use case.

Browse samples →
Frequently Asked Questions

Still deciding? Here's what most teams ask first.

No. MyFitnessPal's official REST API is private and partner-only, requiring an application and approval process. Our infrastructure reverse-engineers the same native mobile API the official app uses, giving you self-serve access to your own account data.

Your own account only. You authenticate with your MyFitnessPal credentials, and the API returns data from your diary, measurements, and goals. We do not provide access to other users' data.

Both. Our client supports reading and writing: log food entries, modify or delete diary entries, log exercise, set weight measurements, and update water intake.

Every request to /v2/diary triggers a live pull from MyFitnessPal's native API — you're not reading from a stale cache. Each response is timestamped.

We handle session management automatically, including Cloudflare bypass and token refresh. Sessions typically last around 30 days, and our infrastructure handles re-authentication transparently.

Yes, every account starts with a free sandbox key and sample data so you can test all endpoints before connecting your own MyFitnessPal account.

Brand Image
▼
INQUIRE NOW