Tiny Plates API
A read API for over 12,000 recipes scraped from the web and normalized into one model. Every public recipe has structured ingredients, numbered steps, times in seconds, servings, nutrition, media, classification and whether it contains each regulated allergen.
Base URL
Every endpoint hangs off one host. There is no version prefix in the path; the current model is version 2 and is described by the OpenAPI document.
https://api.tinyplates.devYour first request
Create a key — it takes a minute and comes with 50 requests a day — then ask for the most popular recipe.
curl 'https://api.tinyplates.dev/popular?limit=1' \
-H 'Authorization: Bearer rd_your_api_key'The quickstart walks through a real request and its response, in curl, JavaScript and Python.
Ways in
The same recipes, whichever way you call them:
- Over HTTP, from any language. The reference below has every endpoint, with a Run button.
- From JavaScript or TypeScript, with the tiny-plates package: typed methods, errors you can check, and paging.
- From a terminal, with the tiny-plates command.
- From Claude, ChatGPT, Cursor or another AI agent, through the MCP server.
Endpoints
13 endpoints, all GET, none of which take a request body.
Recipes
- GET
/searchSearch recipes by meaning as well as wording, across names, ingredients and descriptions, and return only the fields you need. - GET
/recipes/{id}Fetch a single recipe by its id, with structured ingredients, numbered steps, times, nutrition and media, scaled to the number of servings you ask for. - GET
/recipes/{id}/similarRecipes like the one a reader is looking at, served as the same course and keeping to its diet, with a score and the ingredients the two share. - GET
/popularThe best-loved recipes in the database, ranked by rating and by how many people rated them, so one five-star review cannot beat a long-loved favourite. - GET
/recipesBusiness planBusiness plan only. Page through the whole database, newest first, filtered by cuisine, course, category, diet, ingredient, language or total time.
Meal planning
- GET
/pantryRank recipes by how much of them your pantry already covers, with the missing ingredients listed, so you can see what you can cook right now. - GET
/shopping-listTurn several recipes and their serving counts into one shopping list, grouped by aisle, with the amounts of shared ingredients added together.
Ingredients
- GET
/ingredients/resolveTurn ingredient names as people write them, such as "fresh cilantro" or "heavy cream", into the canonical ids the filters and /ingredients/:id take. - GET
/ingredients/{id}One ingredient by its canonical id, with its spellings, allergens, diets, substitutions, density and whether it pours, so a recipe app can reason about it. - GET
/ingredients/{id}/pairingsWhat an ingredient is most often cooked with, counted from real recipes, for "what goes with X" or for filling in a dish. - GET
/substitutionsWhat to use instead of an ingredient, in what amount and how to handle it, and when the swap does not work. An ingredient with no known swap gets no guess. - GET
/ingredientsBusiness planBusiness plan only. The whole ingredient vocabulary, most used first, with every spelling seen per language, so "tomat" and "Tomate" share one id.
Conventions
- Responses are JSON. Errors are always
{ error: { code, message } }— see errors. - Durations are seconds, never formatted strings. Timestamps are ISO 8601.
- A field that is absent is unknown, not empty. The API omits what a source did not publish rather than guessing at it.
cuisines,courses, diets, regulated allergen features and units come from closed lists — see filtering and vocabularies.- List endpoints page with
limitandoffset— see pagination.