Food.com Recipe API: How to Get Nutrition and Protein Data (2026)

A developer's guide to recipe nutrition and protein APIs, 2026 edition. Published by Make An App Like. Reading time: about 12 minutes.

Quick Answer

Food.com does not have a public recipe API. There is no developer portal, no API key signup, and no documented endpoint for recipes, calories, or protein. To get recipe nutrition and protein data programmatically in 2026, use a verified alternative: USDA FoodData Central (free, government-run, authoritative single-food data), Edamam (best ingredient-level recipe analysis), Spoonacular (recipe search plus macros in one call), or Nutritionix (natural-language and branded UPC lookup). All four return calories, protein, fat, carbohydrates, fiber, sugar, and sodium per serving in structured JSON.

Key Takeaways

• No official Food.com API exists. Food.com (owned by Discovery, Inc.) blocks programmatic access via its terms of service and Cloudflare anti-bot protection.
• USDA FoodData Central is the best free option: 1,000 requests per hour, public domain, no attribution required, but no recipe parsing.
• Edamam is best for ingredient-level nutrition, parsing free-text ingredient lists into per-serving protein and macros.
• Spoonacular is best for recipe-first apps, returning a recipe plus full macros in a single call from $5 per month.
• Nutritionix is best for barcode and natural-language lookups, with an 800,000+ item branded UPC database.
• Per-serving vs per-recipe is the classic bug: per_serving = per_recipe / servings. Store and label both.
• Scraping Food.com is not a legal substitute; the Kaggle dataset is fine for research but not for a live commercial app.

Executive Summary

Food.com is one of the largest user-generated recipe portals on the internet, with more than 180,000 community-submitted recipes and roughly 700,000 user reviews. Despite that volume, Food.com does not publish an official, public REST API for accessing recipes, nutrition facts, calories, or protein values. There is no developer portal, no API key signup, and no documented recipe nutrition protein endpoint.

For developers building recipe apps, fitness trackers, or meal-planning tools, this means you cannot legally retrieve nutrition data directly from Food.com. The practical path is to use a verified nutrition API for recipes that already exposes macros, calories, and per-serving protein. The four strongest options in 2026 are the USDA FoodData Central API (free, government-run), Edamam (nutrition plus recipe analysis, paid tiers), Spoonacular (recipe-first with full macros), and Nutritionix (natural-language nutrition lookup).

This article explains exactly how Food.com surfaces nutrition data on its pages, what a hypothetical Food.com recipe API response would look like, and how to choose the best alternative API for your use case. It includes example curl requests, JSON payloads, rate limits, pricing tiers, and a developer-focused FAQ section optimized for Google featured snippets and AI Overviews.

Does Food.com Have a Public Recipe API?

No. As of 2026, Food.com does not offer an official, public recipe API. The site is operated by Discovery, Inc. (the media group behind Food Network and HGTV) and was previously known as GeniusKitchen. There is no developer portal at developers.food.com, no API key signup page, no published OpenAPI or Swagger spec, and no documented recipe nutrition protein endpoint. Developers who try to call api.food.com or scrape recipe pages programmatically are blocked by the site's terms of service and by anti-bot protections such as Cloudflare.

What does exist is a small ecosystem of community-published datasets derived from Food.com's HTML pages. The most widely used is the Food.com Recipes and User Interactions dataset on Kaggle, which contains more than 180,000 recipes and 700,000 recipe reviews scraped from public Food.com pages between 2008 and 2018. A second dataset, Food.com Recipes and Reviews, extends the original with structured nutrition fields for each recipe. These datasets are useful for academic research, recommendation-system training, and natural-language processing experiments, but they are not a substitute for a live API.

If you need real-time, programmable access to recipe nutrition data, you must use a different provider. The four providers covered in this guide (USDA FoodData Central, Edamam, Spoonacular, and Nutritionix) all expose real REST endpoints, return structured JSON, and explicitly allow commercial use under their paid tiers. None of them are affiliated with Food.com, but they all return the same kinds of nutrition fields a Food.com API would return: calories, protein, fat, carbohydrates, fiber, sugar, and sodium per serving.

How Food.com Displays Nutrition and Protein Information

On Food.com, each recipe page contains a Nutrition Information panel that typically appears below the ingredients list and above the user reviews. The panel shows calories, total fat, saturated fat, cholesterol, sodium, total carbohydrates, dietary fiber, sugars, and protein. These values are presented per serving, with the serving size derived from the recipe's stated yield (for example, a recipe that serves 6 will divide all ingredient totals by 6).

Food.com does not calculate these nutrition values itself. Like most large recipe sites, it uses an ingredient-matching pipeline that takes each ingredient line (for example, "1 cup of long-grain white rice") and resolves it against a reference nutrient database, almost always the USDA National Nutrient Database or a commercial equivalent. The pipeline parses quantities, normalizes units (cups to grams, tablespoons to milliliters), and sums the macro contributions per serving. The result is rendered into the page as static HTML.

This pipeline has known accuracy limits. Ingredient matching can fail when a recipe uses brand-name products, regional ingredients, or vague measurements like "a pinch of salt." Values for protein in particular can drift when the recipe calls for mixed protein sources (chicken plus beans plus dairy). For apps where nutrition accuracy is critical, such as clinical diet tracking or fitness coaching, the Food.com display values should be treated as estimates, not laboratory values. Verified nutrition APIs such as Edamam and USDA FoodData Central expose the same kind of ingredient-matching pipeline but let you control the ingredient resolution and serving size, which improves accuracy.

Possible API Response Structure for Protein, Calories, Carbs, and Fat

Because Food.com does not publish an API, the JSON schema below is illustrative. It shows what a recipe API with protein data would look like if Food.com (or any equivalent recipe provider) exposed a recipe nutrition protein endpoint. Use this schema as a reference when you compare alternative APIs, because most of them return a similar shape.

Listing 3.1: Hypothetical Food.com recipe nutrition response (illustrative only, not real)

{
  "recipe": {
    "id": "foodcom-240285",
    "title": "Slow Cooker Chicken Tortilla Soup",
    "source_url": "https://www.food.com/recipe/240285",
    "servings": 6,
    "prep_minutes": 15,
    "cook_minutes": 240,
    "ingredients": [
      { "name": "boneless skinless chicken breasts", "quantity": 1.5, "unit": "lb" },
      { "name": "black beans, canned", "quantity": 15, "unit": "oz" },
      { "name": "corn kernels", "quantity": 1, "unit": "cup" }
    ]
  },
  "nutrition": {
    "per_serving": {
      "calories": 312,
      "protein_g": 28.4,
      "fat_g": 9.2,
      "saturated_fat_g": 2.1,
      "carbohydrates_g": 31.0,
      "fiber_g": 6.8,
      "sugar_g": 4.1,
      "sodium_mg": 540
    },
    "per_recipe": {
      "calories": 1872,
      "protein_g": 170.4,
      "fat_g": 55.2,
      "carbohydrates_g": 186.0
    },
    "serving_size_g": 320,
    "data_source": "USDA FoodData Central (SR Legacy)"
  }
}

Note: this is a hypothetical schema for illustration. Food.com does not expose any such endpoint.

Field Reference

How Developers Can Retrieve Nutrition Data Using Alternative APIs

Since Food.com does not expose a recipe API with protein data, you have to call a different provider. The four APIs below are the most commonly used substitutes in 2026. Each one exposes an HTTP endpoint that accepts either a recipe ID, a list of ingredients, or a free-text food description, and returns a structured JSON object with calories, protein, fat, carbohydrates, and micronutrients.

USDA FoodData Central API

FoodData Central is the USDA's modern nutrient database and the de facto reference source for almost every nutrition API on the market. The API is free, requires only an api.data.gov key, and allows up to 1,000 requests per hour per key. It is the right choice when you need authoritative, government-sourced data and you do not need recipe parsing. FoodData Central returns Foundation Foods, SR Legacy foods, Survey foods, Branded foods, and experimental foods in a single JSON response with full nutrient breakdowns including protein, fat, carbs, fiber, sugar, and a long tail of vitamins and minerals.

Edamam Recipe Analysis API

Edamam sells three separate products: a Food Database API, a Nutrition Analysis API, and a Recipe Search API. The Recipe Analysis API is the most relevant for this guide because it accepts a free-text ingredient list and returns full per-serving nutrition including protein. Edamam is a strong choice for fitness and diet-tracking apps because it can resolve arbitrary ingredient text such as "1 cup cooked quinoa, 100g grilled chicken breast" into structured nutrition data. Pricing starts at around $29 per month for the Wellness tier and scales to $499 per month for the Dietitian tier with commercial rights.

Spoonacular Recipe and Food API

Spoonacular is the only major provider that combines recipe search, ingredient parsing, nutrition estimation, and meal planning in a single API. The free tier allows 150 requests per day, and paid tiers range from $5 to $149 per month depending on request volume. Spoonacular is recipe-first, which means it can return a recipe with full macros and ingredient list in a single call. For apps that need to display a recipe card with nutrition, Spoonacular is usually the most efficient option.

Nutritionix API

Nutritionix specializes in natural-language nutrition lookup. Its flagship endpoint accepts a free-text query such as "1 large apple and a tablespoon of peanut butter" and returns a structured nutrition object. Nutritionix also exposes a branded-foods database with more than 800,000 UPC items, which is useful for barcode-scanning fitness apps. The free tier is limited, and commercial pricing is negotiated per application.

Comparison Table

Example Requests and JSON Responses

Below are three working curl examples using the verified APIs. Replace the placeholder API keys (DEMO_KEY, YOUR_EDAMAM_APP_KEY, YOUR_SPOONACULAR_KEY) with your own credentials from each provider's developer portal.

USDA FoodData Central: Search by Food Name

Request:

curl -s "https://api.nal.usda.gov/fdc/v1/foods/search?api_key=DEMO_KEY&query=chicken%20breast%20grilled&pageSize=1"

Response (truncated):

{
  "totalHits": 1248,
  "foods": [
    {
      "fdcId": 1734090,
      "description": "Chicken, broilers or fryers, breast, meat and skin, cooked, grilled",
      "dataType": "Foundation",
      "foodNutrients": [
        { "nutrientName": "Protein", "value": 30.99, "unitName": "G" },
        { "nutrientName": "Energy", "value": 185, "unitName": "KCAL" },
        { "nutrientName": "Total lipid (fat)", "value": 7.78, "unitName": "G" },
        { "nutrientName": "Carbohydrate, by difference", "value": 0.0, "unitName": "G" }
      ]
    }
  ]
}

Edamam Recipe Analysis: POST Ingredient List

Request:

curl -s -X POST "https://api.edamam.com/api/nutrition-details?app_id=YOUR_APP_ID&app_key=YOUR_EDAMAM_APP_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Chicken Tortilla Soup",
    "yield": 6,
    "ingr": ["1.5 lb boneless skinless chicken breasts", "15 oz canned black beans", "1 cup corn kernels"]
  }'

Response (truncated):

{
  "yield": 6,
  "calories": 1872,
  "totalWeight": 1920,
  "totalNutrients": {
    "PROCNT": { "label": "Protein", "quantity": 170.4, "unit": "g" },
    "ENERC_KCAL": { "label": "Energy", "quantity": 1872, "unit": "kcal" },
    "FAT": { "label": "Total lipid (fat)", "quantity": 55.2, "unit": "g" },
    "CHOCDF": { "label": "Carbohydrate, by difference", "quantity": 186, "unit": "g" }
  },
  "totalDaily": {
    "PROCNT": { "label": "Protein", "quantity": 341, "unit": "%" }
  }
}

Spoonacular: Recipe by ID with Nutrition

Request:

curl -s "https://api.spoonacular.com/recipes/654959/information?apiKey=YOUR_SPOONACULAR_KEY&includeNutrition=true"

Response (truncated):

{
  "id": 654959,
  "title": "Pasta With Tuna",
  "servings": 2,
  "nutrition": {
    "nutrients": [
      { "name": "Calories", "amount": 414.62, "unit": "kcal" },
      { "name": "Protein", "amount": 27.39, "unit": "g" },
      { "name": "Fat", "amount": 11.79, "unit": "g" },
      { "name": "Carbohydrates", "amount": 47.62, "unit": "g" }
    ]
  }
}

Per-Serving vs Per-Recipe Nutrition Values

One of the most common bugs in recipe nutrition apps is mixing up per-serving and per-recipe values. Most nutrition APIs return both, and they are not interchangeable. Per-serving values are what you show to a user who is logging a single meal. Per-recipe values are what you use when you store the recipe in a database or compute grocery costs. Getting these backwards can produce calorie counts that are off by a factor of 6 or 8.

The conversion is simple: per_serving = per_recipe / servings. For example, the chicken tortilla soup above has 1,872 calories per recipe and serves 6, so each serving is 312 calories. The same logic applies to protein: 170.4 grams of protein per recipe divided by 6 servings gives 28.4 grams per serving. Always store both values in your database and label them clearly in your UI so users can scale portions without re-calling the API.

Table: Worked example, Chicken Tortilla Soup (serves 6)

Daily values are based on the FDA 2,000-calorie reference diet.

API Accuracy, Rate Limits, Pricing, and Commercial Use

When you choose a nutrition API for recipes, four dimensions matter: accuracy of the underlying nutrient database, rate limits on the free tier, pricing for production volume, and the commercial-use clause in the terms of service. The table below summarizes the four providers and is current as of 2026.

Accuracy

All four providers ultimately derive their nutrient values from the USDA National Nutrient Database, but they differ in how they resolve ingredient text. USDA FoodData Central is the most authoritative because it is the source. Edamam adds a matching layer for free-text ingredients, which can introduce small errors when ingredient names are ambiguous. Spoonacular runs an ingredient parser on recipe text, which works well for English-language recipes but can fail on regional cuisines. Nutritionix focuses on branded and packaged foods, where accuracy is high because the data comes from manufacturer labels.

Rate Limits

USDA FoodData Central is by far the most generous free option, with 1,000 requests per hour. Spoonacular allows 150 requests per day on the free tier, which is enough for prototyping but not for production. Edamam and Nutritionix both offer limited free trials meant for evaluation only; production use requires a paid key. If you expect more than 100,000 requests per month, contact each provider directly for negotiated volume pricing.

Pricing

Spoonacular is the cheapest entry point at $5 per month for the basic tier, and scales to $149 per month for 100,000 requests. Edamam is more expensive but offers deeper nutrition analysis; the Wellness tier starts at $29 per month and the Dietitian tier (which includes clinical-grade nutrition labeling) costs $499 per month. USDA FoodData Central is free for any volume within the rate limit. Nutritionix does not publish list pricing and typically negotiates per application.

Commercial Use

USDA FoodData Central data is in the public domain and can be used commercially without attribution. Edamam, Spoonacular, and Nutritionix all require attribution on the free tiers and explicitly allow commercial use on paid tiers. If your app displays nutrition data next to advertising, paid subscriptions, or premium features, you must be on a paid tier of the commercial API. Read each provider's terms of service carefully, because the rules around caching, redistribution, and white-label use vary.

Best API Recommendation for Recipe or Fitness Apps

The best API depends on what your app actually does. There is no single winner, but there is a clear decision tree. Use the recommendations below to choose.

If you are building a recipe or fitness app, start with Spoonacular's free tier to prototype the recipe-search and meal-planning flow, then layer in Edamam for any feature where users enter custom ingredient text. Use USDA FoodData Central as a fallback for any ingredient that neither provider can resolve, because FoodData Central has the deepest coverage of generic and Foundation Foods. If you are scoping the wider product around one of these APIs, our breakdown of what a SaaS MVP really costs puts the API subscription in the context of the full build, and our grocery delivery app guide covers the adjacent architecture for food-focused products.

Building a Recipe or Nutrition App With Make An App Like

Make An App Like has shipped 500+ applications for founders in 40+ countries since 2016, including food, recipe, and fitness products that integrate exactly these nutrition APIs. When we build one, we wire in the API that fits the use case, add a caching and fallback layer so you are not paying per call for repeat lookups, and store per-serving and per-recipe values correctly so the portion math never breaks. If an off-the-shelf API does not cover your ingredients or market, we build the resolution layer to fill the gaps.

Estimate Your Recipe or Fitness App Build

Want a line-item budget for a recipe, nutrition, or fitness app built on these APIs? Use our free calculator: https://makeanapplike.com/tools/app-cost-calculator

Launch Faster With a Ready-Made Foundation

Skip months of build time with a white-label app foundation, API-ready from day one: https://makeanapplike.com/buy-white-label-apps

Conclusion

There is no Food.com recipe API, and no legal way to pull its nutrition data programmatically, but that is not the obstacle it first appears to be. Every nutrition value Food.com displays comes from the USDA database, and four verified APIs expose that same data with real endpoints, structured JSON, and commercial licensing. Choose USDA FoodData Central for free authoritative data, Edamam for ingredient-level analysis, Spoonacular for recipe-first apps, and Nutritionix for branded and barcode lookups. Store per-serving and per-recipe values separately, add a caching layer to control costs, and your app will have cleaner, more accurate nutrition data than scraping Food.com could ever provide.

Source References

All sources were verified in 2026. URLs are reproduced as published by each provider.

1. USDA FoodData Central API Guide: fdc.nal.usda.gov/api-guide
2. Edamam Food Database API Documentation: developer.edamam.com/food-database-api-docs
3. Edamam Nutrition Analysis API: developer.edamam.com/edamam-nutrition-data-api
4. Spoonacular API Documentation: spoonacular.com/food-api/docs
5. Nutritionix Developer Portal: nutritionix.com/business/api
6. Food.com Recipes and User Interactions (Kaggle Dataset): kaggle.com
7. Food.com Recipes and Reviews (Kaggle Dataset): kaggle.com
8. GreenChoice: Best Nutrition Databases and Nutrition APIs (2026)
9. Calorie API: Comparison of Calorie API vs USDA, FatSecret, Edamam, Nutritionix
10. ymove.app: Top 8 Nutrition APIs in 2026 (Compared)
11. Suggestic Blog: 17 Most Popular Food APIs
12. Suggestic Blog: 11 Most Popular Recipe APIs