Skip to content
Recipe API

Use Case Guide

Recipe API for Calorie Tracking Apps

Calorie counters live or die on data accuracy. Recipe API returns 32 tracked nutrients per serving on every recipe — calories, protein, carbs, fat, fiber, sugar, sodium and more — each traceable to USDA FoodData Central. Filter recipes by max_calories and min_protein, then render exact per-serving totals straight into your app.

Free discovery. Full recipe detail uses one credit. Commercial use and caching start on Developer.

  • Search, filters, and generation
  • 32 USDA-backed nutrients
  • One consistent schema
  • No attribution required

Typical Builder Journey

1. Filter by calorie budget
Surface recipes that fit a daily or per-meal calorie target with a single query.
GET /api/v1/recipes?max_calories=500
2. Add protein and macro goals
Combine min_protein with calorie limits to balance satiety against the budget.
GET /api/v1/recipes?max_calories=500&min_protein=25
3. Render 32 per-serving nutrients
Pull full nutrition for any recipe — calories, fiber, sugar, sodium and 28 more — per serving.
GET /api/v1/recipes/{slug}
4. Trust the source data
Every ingredient links to USDA FoodData Central, so per-serving numbers are traceable, not estimated.

Calorie Tracking Query Example

Find lower-calorie, high-protein recipes for a calorie counter feed.

GET /api/v1/recipes
curl "https://recipe-api.com/api/v1/recipes?max_calories=500&min_protein=25&per_page=20" \
  -H "X-API-Key: rapi_your_key"

Related Guides

Start Building

32 per-serving nutrients on every recipe, traceable to USDA data. Filter by calories and protein out of the box.