The best recipe APIs in 2026, free and paid, compared

Picking a recipe API looks easy at first. They all return a title and a nice photo. The differences show up later. Can you scale the recipe? Are you allowed to keep it in your database? What happens to the bill when your app takes off?

A quick heads-up: we run one of these APIs. So take our view with a pinch of salt. We've tried hard to be fair, though, and we'll tell you when another one is the better pick. Every price here comes from the provider's own site, checked in October 2026. Prices change, so have a look before you commit.

First, what do you actually need? For most projects it comes down to five things:

• Structured ingredients. "2 cups flour" as a number, a unit and a name. Not one string you have to pick apart yourself. You need this for scaling, shopping lists and nutrition.
• Search that finds things. By name at the very least. By ingredient, diet or allergen if you can get it.
• Steps and images in the response. Some APIs link out to the source for the method. That's fine for a search page. It's not fine for a cooking app.
• Terms you can live with. How long can you cache? Do you need a backlink? Is commercial use allowed on the free plan?
• A price that works. Both today and at ten times the traffic.

Here's how the recipe APIs still around in 2026 stack up.

The options

Spoonacular is the big all-rounder. One key gets you recipe search, grocery products, restaurant menu items, meal plans and more. Its site lists 5,000+ recipes, 600K+ products and 115K+ menu items. If you need food data beyond recipes, it's hard to beat.

It charges in points, not requests. A recipe search costs 1 point plus 0.01 per result, and some options cost extra. The free plan gives you 50 points a day at 1 request per second, and you need to put a backlink to Spoonacular on your site. Paid plans are $29 a month (1,500 points a day), $79 (4,500) and $149 (10,000). Enterprise starts at $300. The paid plans come with an uptime promise too: 99%, or 99.9% on the $149 plan.

The catch is in the terms. You may cache data for an hour at most, and only with written permission. The recipe id, title and image URL can stay forever, but nothing else. If you stop using the API, you're meant to delete everything you got from it. So you can't slowly build your own recipe library on top of it. We go deeper in Tiny Plates vs Spoonacular.

Edamam has the biggest index by far: over 2 million recipes from around the web. Ingredients come back structured, with a quantity, a measure and a food. The diet and health filters are thorough, and nutrition is what Edamam does best.

There's no free plan for Recipe Search, though. It's $9 a month for 10,000 calls, $99 for 500,000 and $399 for a million. Above that it's custom. Some plans have a 10-day trial. On the $9 and $99 plans you get web recipes without the cooking steps, so you link out to the source for those. Steps only come with the 20,000 Edamam-owned recipes on the $399 plan. You may cache the recipe id and name, plus four nutrition numbers from the $99 plan up. Attribution is required on every plan.

One more thing. Edamam's pricing page says requests must be driven by a human end user, and automated requests aren't allowed. If you're building an agent or a batch job, read that part closely. More in Tiny Plates vs Edamam.

TheMealDB is the classic first recipe API. No sign-up, a test key of 1 and a handful of simple endpoints. It had 793 meals when we checked. Each ingredient is a name plus a measure written as text, like "1 tbsp" or "a pinch". The method is one block of text. It's lovely for learning, teaching and hackathons.

The test key is meant for development and education. If you release an app publicly, you're asked to become a supporter, which is a one-off $10. That also unlocks multi-ingredient filters and a random meal endpoint. See Tiny Plates vs TheMealDB.

API Ninjas has a recipe endpoint with over 125,000 recipes, according to its docs. Ingredients come with a name, quantity and unit, along with servings, instructions and nutrition. The free plan is 3,000 calls a month and is for evaluation only, so no commercial use. Ingredient search and rescaling are premium features. Paid plans are on their pricing page. It's a good pick if you already use API Ninjas for other things.

FatSecret Platform is mostly a nutrition and food database, but it has recipes too, with images, directions, ingredients and nutrition. The free Basic tier allows 5,000 calls a day, with US data only and attribution required. Startups, non-profits and students can apply for Premier Free. The paid Premier tier is priced on request. Pick this one if nutrition tracking is the heart of your app and recipes are a side dish.

Tasty on RapidAPI serves recipes from BuzzFeed's Tasty. It's a third-party listing by a publisher called Api Dojo, and you subscribe through RapidAPI. The listing wouldn't load for us, so check RapidAPI for current plans. Just know that you'd depend on a middleman. More in Tiny Plates vs Tasty.

Yummly is gone. Its API closed in 2019, and the app and website went offline in December 2024. If an old tutorial sends you there, it's time to move on. We wrote up what to use instead.

Tiny Plates is ours. It's free: 50 requests a day and 300 a week per account. No credit card, and we raise the limit if you ask. There's no paid plan yet, and no uptime promise either. We have thousands of recipes, gathered from public recipe pages, in English, Spanish and Swedish.

What we care about most is the recipe itself. Every ingredient has its quantity, unit, name and preparation in separate fields. It also gets an ingredient id that means the same thing in every language. Here's a real line from a coconut curry:

{
  "display": "1 can chickpeas, rinsed and drained",
  "ingredientId": "chickpea",
  "name": "chickpea",
  "optional": false,
  "original": "1 can chickpeas, rinsed and drained",
  "preparation": "rinsed and drained",
  "quantity": { "unit": "can", "value": 1 }
}

Steps come back numbered. Every recipe says which of 16 allergens it contains, so you can filter them out of a search:

curl 'https://api.tinyplates.dev/search?query=weeknight%20curry&without=milk,peanuts&limit=5' \
  -H 'Authorization: Bearer rd_your_api_key'

Search works on meaning, so "creamy pasta" finds carbonara. On top of that you get cooking from what's in the fridge, scaling, metric and imperial conversion, substitutions and shopping lists. You may cache the recipes your users ask for. You just can't copy the whole index. Credit the source and link to it.

The honest downsides? Far fewer recipes than Edamam or API Ninjas. No grocery products or restaurant menus. No paid plan with an uptime promise. And three languages so far.

Here's a little app built on it. Tell it what's in your fridge:

Side by side

API	Free tier	Paid from	Recipes	Steps in the response
Spoonacular	50 points a day, backlink required	$29/month	5,000+, plus products and menus	Yes
Edamam	None (10-day trial on some plans)	$9/month	2 million+ web recipes	Only on the $399 plan
TheMealDB	Test key for development	$10 once	793	One block of text
API Ninjas	3,000 calls a month, non-commercial	See their pricing page	125,000+	Yes
FatSecret	5,000 calls a day, US data, attribution	On request	Part of a nutrition database	Yes
Tasty (RapidAPI)	Set on RapidAPI	Set on RapidAPI	Tasty's recipes	Check the listing
Tiny Plates	50 a day, 300 a week	No paid plan yet	Thousands	Yes, numbered

A table only tells you so much. Here are the things that tend to bite later.

Count your calls the way you'll really make them. A recipe page often needs a search and then a lookup. On a points system, the cost also grows with the number of results. A Spoonacular search for 10 recipes is 1.1 points, so the free 50 points cover about 45 of those a day, before you open a single recipe. Write down the calls one screen makes, then multiply by your users.

Read the caching rules before you design your database. This one changes your whole app. If you can only keep an id and a title, every recipe view is a live API call. That's slower, and it costs money on a paid plan. If you can cache what your users open, you can save favourites and work offline.

Check what the free plan allows. Several free tiers are for testing only. API Ninjas doesn't allow commercial use on its free plan. TheMealDB asks you to become a supporter before you ship publicly. Spoonacular's free plan needs a backlink. None of that is unreasonable. It's just easy to miss until launch day.

Look at real ingredient lines. Make the same request on two APIs and compare. Is "1 can chickpeas, rinsed and drained" one string, or a quantity, a unit, a name and a preparation? If you ever want to scale a recipe or add up a shopping list, this matters more than the size of the index.

Think about the steps. If people will cook from your app, the method has to be in the response. Linking out is fine for discovery. It's annoying with floury hands.

So which one should you pick?

It really depends on what you're making.

A hobby project or a class. If you just want a recipe on screen, TheMealDB is the quickest start. No sign-up at all. If you want to scale recipes, build shopping lists or filter allergens, Tiny Plates gives you that for free.

A production app with a budget. Spoonacular, if you need grocery products, menus or meal plans from one API, plus an uptime promise. Edamam, if you need millions of recipes and great nutrition data, and linking out for the steps is fine.

A nutrition or fitness app. FatSecret or Edamam. Nutrition is their thing.

An AI agent. Tiny Plates has an MCP server. Your agent signs in with your account and gets tools for search, scaling, pantry matching and shopping lists. Spoonacular has an MCP server too. Whichever you choose, check the terms on automated use first.

Recipes that aren't in English. Tiny Plates has Spanish and Swedish recipes, written in their own language. Add language=es or language=sv to a search. The ingredient ids are shared, so "tomat" in a Swedish recipe and "tomate" in a Spanish one point to the same ingredient.

You can also mix and match. Plenty of apps use one API for nutrition and another for recipes.

If Tiny Plates sounds like a fit, grab a free key and send your first search. It takes about a minute.