Skip to content

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.dev

Your 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.

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 limit and offset — see pagination.