Skip to content
Skip to Content
Docs
Studio

Get Ingredient Usage

List the organization's recipes that pin ingredient_id — standard or custom. Backed by an eventually-consistent, near-real-time reverse index; not a hard read-your-writes guarantee immediately after a recipe save.

version_id is applied as a DynamoDB filter after the page is read, so a filtered page can return fewer than limit items — possibly zero — even when more matches exist further in. An empty page with meta.has_more: true is not an empty result set: keep paging with meta.cursor until meta.has_more is false. Unfiltered pages are unaffected.

GET
/studio/ingredients/{ingredient_id}/usage

Path Parameters

ingredient_id*Ingredient Id

Ingredient ID (standard or custom)

Query Parameters

limit?Limit

Maximum number of recipes to return (1-100).

Range1 <= value <= 100
Default20
cursor?|

Opaque pagination cursor returned in meta.cursor from a previous response. Omit on the first page.

version_id?|

Narrow to recipes pinned at exactly this custom-ingredient version. Omit to return recipes pinning any version. Applied after the page is read, so a filtered page can be short or empty while more matches exist further in.

Response Body

Successful Response

application/json
  1. response

Response for the get-ingredient-usage endpoint.

data*array<>
meta*

Paginated response metadata.

Example Request
curl -X GET 'https://api.bettermenu.live/studio/ingredients/string/usage'
Example Response
{  "data": [    {      "recipe_id": "string",      "recipe_name": "string",      "recipe_status": "string",      "source": "standard",      "pinned_version_id": "string"    }  ],  "meta": {    "version": "string",    "request_id": "string",    "timestamp": "string",    "cursor": "string",    "has_more": true  }}

Recipe in, FDA-format Nutrition Facts out, with every version kept.

Start freeNo card needed.