# Mealz Recipes API

> 6,700+ French recipes from Mealz (Miam) with ingredients, quantities, steps, times and cost

- Vendor: `mealzrecipesapi` · version 1.0 · category Food · tags recipes api, french recipes api, recipe ingredients api, mealz api, miam api, meal planning api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/mealzrecipesapi
- This document: https://apiclay.com/docs/mealzrecipesapi.md
- OpenAPI 3.1: https://apiclay.com/api/mealzrecipesapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `mealzrecipesapi`
- Updated: 2026-11-18

## About

## Mealz Recipes API

The recipe catalogue of Mealz (formerly Miam), the recipe-to-basket service used by French supermarket sites such as Courses U: about 6,750 recipes searchable by title, each with servings, preparation, cooking and resting times, difficulty, estimated cost, popularity, photo and video; its ingredient list with quantity, unit and picture; its numbered preparation steps; and the recipe types. Content is in French.

Data comes from **mealz.ai** (https://www.mealz.ai). Every route calls the source's own public API and returns it unchanged.

Typical flow: `/recipes?filter[title]=poulet&amp;page[size]=20`, then `/recipe?id=&amp;include=ingredients,recipe-steps`.

### Routes

#### GET `/recipes` - Search recipes
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| filter[title] | query | string | no | Words in the title, in French (e.g. `poulet`). |
| page[size] | query | number | no | Items per page, e.g. `20`. |
| page[number] | query | number | no | Page, from 1. |

Returns: JSON:API `data` array of recipes (`id`, `attributes`: `title`, `description`, `slug`, `number-of-guests`, `preparation-time`, `cooking-time`, `preheating-time`, `resting-time` as ISO 8601 durations, `difficulty`, `cost`, `computed-cost` in euros, `popularity`, `media-url`, `video-id`), `meta.record-count` and `links` for paging.

#### GET `/recipe` - Recipe
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| id | path | number | yes | Recipe `id` from `/recipes`. |
| include | query | string | no | Related records to embed, e.g. `ingredients,recipe-steps`. |

Returns: `data` (one recipe, same attributes) plus `included` with the requested ingredients and steps.

#### GET `/ingredients` - Recipe ingredients
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| id | path | number | yes | Recipe `id` from `/recipes`. |
| page[size] | query | number | no | Items per page, e.g. `20`. |
| page[number] | query | number | no | Page, from 1. |

Returns: `data` array of `ingredients`: `name`, `quantity`, `unit`, `importance` (primary or secondary), `picture-url`; `meta.record-count`.

#### GET `/steps` - Recipe steps
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| id | path | number | yes | Recipe `id` from `/recipes`. |

Returns: `data` array of `recipe-steps`: `step-number`, `title`, `description`, `media-url`.

#### GET `/recipe-types` - Recipe types
No parameters.

Returns: `data` array of `recipe-types` (dessert, boisson, plat principal, entrée, autre) with `name`.

### Caveats

- Recipes and photos belong to Mealz and its recipe partners. `computed-cost` is Mealz's estimate, not a store price.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by mealz.ai.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /recipes — Search recipes
- Gateway: `GET https://api.apiclay.com/v1/api/mealzrecipesapi/recipes`
- Public query params: `filter[title]` (string), `page[size]` (number), `page[number]` (number)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /recipe — Recipe
- Gateway: `GET https://api.apiclay.com/v1/api/mealzrecipesapi/recipe`
- Public query params: `include` (string), `id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /ingredients — Recipe ingredients
- Gateway: `GET https://api.apiclay.com/v1/api/mealzrecipesapi/ingredients`
- Public query params: `page[size]` (number), `page[number]` (number), `id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /steps — Recipe steps
- Gateway: `GET https://api.apiclay.com/v1/api/mealzrecipesapi/steps`
- Public query params: `id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /recipe-types — Recipe types
- Gateway: `GET https://api.apiclay.com/v1/api/mealzrecipesapi/recipe-types`
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/mealzrecipesapi/recipes" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
