Skip to content

6 Best Recipe APIs in 2026

The recipe APIs you can sign up for today, what each is good at, and the ones that have closed.

Checked September 2026 from each API’s own pages. We make Tiny Plates.

We make one of these, so we say where the others are the better pick.

Quick comparison: the best recipe APIs

ProductBest forStarting priceKey difference
Tiny PlatesBest for: computing with a recipeStarting price: Free, then $5 a month
SpoonacularBest for: groceries, menus and meal plansStarting price: Free, then $29 a month
EdamamBest for: the largest recipe indexStarting price: $9 a month
TheMealDBBest for: learning and demosStarting price: Free test key, $10 once to go public
TastyBest for: BuzzFeed’s Tasty recipesStarting price: See the RapidAPI listing
API NinjasBest for: nutrition figures on every planStarting price: Free to evaluate, then $59 a month

1. Tiny Plates

Free, then $5 a month

Tiny Plates is a recipe API for apps and agents that need to compute with a recipe, not only show it. It is the smallest and newest API on this list.

What it does

  • Quantity, unit, name and preparation in separate fields, with canonical ingredient ids shared across languages.
  • Numbered steps in the response.
  • True or false for each of the EU’s 14 regulated allergens, plus the US definitions of wheat and tree nuts. Informational only.
  • Search by meaning as well as wording.
  • Pantry matching, shopping lists grouped by aisle, serving scaling, metric and imperial conversion, and substitutions.
  • Recipes in English, Spanish and Swedish.

What to watch for

  • Over 12,000 recipes, far fewer than Edamam or API Ninjas.
  • No grocery products or restaurant menus.
  • No uptime promise.

Here is one ingredient line as the API returns it. The quantity, unit and preparation are separate fields, so your code can use them without parsing text.

{
  "ingredients": [
    {
      "display": "1 can white beans or chickpeas, rinsed",
      "name": "white beans or chickpeas",
      "optional": false,
      "original": "1 can white beans or chickpeas, rinsed",
      "preparation": "rinsed",
      "quantity": {
        "unit": "can",
        "value": 1
      }
    }
  ]
}

A free plan with no credit card. Personal is $5 a month and Business $20, with extra requests at $1 per 1,000.

2. Spoonacular

Free, then $29 a month

Spoonacular is the widest food API you can sign up for. One key covers recipe search, grocery products, restaurant menu items, meal plans and shopping lists. It charges in points rather than requests, and its terms limit how long you may keep what you fetch.

Pick it when

  • You need grocery products or restaurant menu items from the same API.
  • You need meal planning built in.
  • You need an uptime promise.

What to watch for

  • Paid plans start at $29 a month.
  • Cached data must be deleted after an hour.
  • The free plan requires a backlink.

See Tiny Plates vs Spoonacular

3. Edamam

$9 a month

Edamam sells several food APIs separately. Its Recipe Search API indexes over 2 million recipes from around the web. Edamam does not hold a licence to most of them, so the API links out to the source for the cooking steps.

Pick it when

  • You need a corpus of millions of recipes.
  • You need hundreds of thousands of calls a month at a flat price.

What to watch for

  • No free plan for Recipe Search.
  • Web recipes link out for the cooking steps.
  • You can cache the recipe id and name, plus four figures from $99 a month.

See Tiny Plates vs Edamam

4. TheMealDB

Free test key, $10 once to go public

TheMealDB is a community-built recipe database with a free JSON API. It is a common first recipe API: there is a test key, no sign-up, and a handful of simple endpoints.

Pick it when

  • You are learning, teaching or building a demo.
  • You want no sign-up and no daily allowance.
  • A few hundred recipes are enough.

What to watch for

  • Ingredients and measures are plain text.
  • 793 meals when we checked.
  • No allergen data.

See Tiny Plates vs TheMealDB

5. Tasty

See the RapidAPI listing

Tasty is BuzzFeed’s food brand, known for its recipe videos. The Tasty API on RapidAPI is a listing published by Api Dojo that returns Tasty’s recipe data. You subscribe to it through RapidAPI.

Pick it when

  • You want Tasty’s own recipes, which we do not have.
  • You already buy your APIs through RapidAPI.

What to watch for

  • You depend on a third-party publisher and a marketplace.
  • You only get recipes from Tasty.
  • We could not read its plans, so check the listing.

See Tiny Plates vs Tasty

6. API Ninjas

Free to evaluate, then $59 a month

API Ninjas is a collection of small APIs under one key. Its Recipe API lists over 125,000 recipes. Searching by ingredient, paging and scaling servings need a paid plan.

Pick it when

  • You need nutrition figures with every recipe.
  • You want a large corpus. Its site lists over 125,000 recipes.
  • You already use its other APIs and want one key for all of them.

What to watch for

  • The free plan does not allow commercial use or storing data.
  • Ingredient search and paging need a plan from $59 a month.
  • No allergen fields listed.

See Tiny Plates vs API Ninjas

APIs that have shut down

Older lists still recommend these. Do not plan a product around them.

  • Yummly. The API shut in September 2019 and the app and website went offline in December 2024. Yummly API alternatives

Which one is right for you?

  • You want to compute with a recipe, not only show it.Tiny Plates
  • You need grocery products or restaurant menu items from the same API.Spoonacular
  • You need a corpus of millions of recipes.Edamam
  • You are learning, teaching or building a demo.TheMealDB
  • You want Tasty’s own recipes, which we do not have.Tasty
  • You need nutrition figures with every recipe.API Ninjas

To try Tiny Plates, follow the quickstart and get a response in a couple of minutes.

Create a free account

The terms say what you may cache and how to credit a recipe, and the overview lists every recipe API we have compared. If something here has changed, write to chris@pullpanda.io and we will correct it.