YMove vs Edamam: Recipe API Comparison

Edamam licenses recipes from a large network of food publishers and runs them through an in-house parser to produce structured ingredient data. The result is broad coverage (hundreds of thousands of recipes) and reasonable per-recipe nutrition.

YMove's recipe corpus is smaller and curated, with each ingredient mapped to a USDA FoodData Central row. That makes the per-ingredient nutrition more consistent (no parser ambiguity) and lets you re-scale, swap ingredients, or render a clean nutrition label without follow-up calls.

Most apps that need recipe search also need a food database for free-form food logging, barcode scanning, and macro tracking. With Edamam, that means subscribing to two products (Recipe Search + Food Database, or Recipe Search + Nutrition Analysis). With YMove, the same API key gets you all of it, plus the exercise side. Compare in detail on the nutrition vs Edamam page.

# Edamam: search recipes
GET /search?q=chicken&diet=high-protein (Recipe Search API)

# YMove: equivalent
GET /api/v2/recipes/search?query=chicken&diet=high_protein

# Edamam: recipe details (re-fetch by URI)
GET /search?r=URI

# YMove: recipe details by slug
GET /api/v2/recipes/{slug}

Edamam wins on raw recipe count and breadth. If your product needs to surface hundreds of thousands of cooking blog recipes, Edamam has the licensing in place. YMove wins on per-ingredient nutrition fidelity, bundled pricing, and shipping recipe + nutrition + exercise content under one key.