Meal planning
Food API for Meal Planning Apps
Meal planners are constraint solvers: hit protein targets, respect calorie budgets, vary the menu. That only works when every candidate food carries consistent, complete macro data, which is exactly what per-100g normalization and the verified-foods filter provide.
Resolve each ingredient with food search, aggregate macros by quantity, and score plans against user targets. Reference endpoints for nutrients, brands, and categories power filter UIs and dietary constraints.
Why teams choose us
Built for your product's hardest problems
Plans are only as good as the data
Complete macro data is guaranteed on every search result, no null-handling in the middle of your solver.
Ingredient quantities need a common baseline
Per-100g normalization makes aggregating a recipe one multiplication per ingredient.
Users want brand-level choices
Brand filters and branded-product coverage let plans reference the actual products users buy.
How it maps
Product needs → API endpoints
Each need in your roadmap maps to a documented endpoint you can try in the playground today.
| Product need | Endpoint |
|---|---|
| Ingredient resolution | GET /search/foods |
| Macro aggregation | GET /foods/{id} |
| Dietary filter UIs | GET /foods/categories/ |
| Nutrient taxonomy | GET /foods/nutrients/ |
Food API for Meal Planning Apps: frequently asked questions
Can I analyze a whole recipe in one call?
There is no recipe-ingestion endpoint. Resolve ingredients individually with search and aggregate by quantity. Cached food IDs make repeat plan generation nearly free.
How do I keep generated plans within quota?
Plan generation reads from your cached ingredient pool rather than live-searching every candidate. A few hundred cached foods cover most planners’ menus.
Does the API support dietary restrictions?
Barcode responses include ingredients and allergen lists when the source provides them, and category data supports building your own dietary filters.
Ship nutrition features this sprint
Create a free account, explore the playground, and integrate with your stack using our framework guides.