Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.spotzee.com/llms.txt

Use this file to discover all available pages before exploring further.

A synthetic food data generator creates sample dish, cuisine, ingredient, meat, spice, fruit and vegetable values for tests, demos and fixture files. It gives teams repeatable food-shaped data without copying production menus, recipe records or catalogue content into lower-control environments.
Generate sample food data at spotzee.com/tools/food-generator.

​
Why this matters

Recipe apps, restaurant demos, food catalogues and content workflows need values that feel realistic enough to exercise UI states. Real menus and product records don’t belong in seed files, support screenshots or automated test logs. Food fields expose common product issues. Dish names wrap, descriptions run long, cuisine filters need varied labels, and ingredient fields need enough variety to test search and validation. But static fixture lists get stale quickly. Generated values are test fixtures only. They do not include verified nutrition facts, allergens, calories or recipe instructions. Each Extended API call deducts a small per-call amount from your Spotzee credit balance. See the Spotzee pricing page for live per-tool pricing.

​
How it works

1

Send the request

POST to /generic/data/generate/food with count. The count is a string from 1 to 100.
2

Choose a method

Use method=profile for expanded food records, or choose one field method such as dish, ingredient, spice, fruit or vegetable.
3

Set locale and seed

Send locale when regional output matters and an optional numeric seed when you need repeatable fixtures.
4

Read the response

The response returns data.foods[], generated, locale, optional seed, and the resolved method. Profile records can include dish, description, cuisine, adjective, ingredient, meat, fruit, vegetable and spice fields.

​
Method reference

MethodOutputMain parameters
profileExpanded food profilecount, locale, seed
adjectiveFood adjective fixturecount, locale, seed
descriptionFood description fixturecount, locale, seed
dishDish-name fixturecount, locale, seed
ethnicCategoryCuisine or regional categorycount, locale, seed
fruitFruit-name fixturecount, locale, seed
ingredientIngredient-name fixturecount, locale, seed
meatMeat or protein fixturecount, locale, seed
spiceSpice-name fixturecount, locale, seed
vegetableVegetable-name fixturecount, locale, seed
Use profile when you need fuller food test data. Use a field method when your form, table, search index or import job only needs one value type.

​
What to watch for

  • Count outside 1 to 100. One request generates up to 100 food records. For more rows, call the endpoint again and vary the seed when you need a different batch.
  • Wrong method for the fixture. Use profile for fuller food records, or a field method for one value type.
  • Invalid seed. Seeds must be whole numbers. Leave the field blank for random output, or reuse a numeric seed for repeatable fixtures.
  • Expecting nutrition data. Generated food values are synthetic sample text. They do not include nutrition facts, allergens, calories or verified recipe instructions.
  • Assuming cuisine accuracy. ethnicCategory is a generated cuisine or regional label for fixture coverage, not a verified culinary classification.

​
FAQs

A synthetic food data generator can return foods[] records with method and value fields. Profile output can also include dish, description, ethnicCategory, adjective, ingredient, meat, fruit, vegetable and spice fields. The exact fields depend on the selected method.
This random food generator is built for test data, not personal meal planning. It creates synthetic dish, ingredient and menu values for QA datasets, prototypes and fixture files.
Yes. Set a numeric seed to reproduce output for the same count, locale and method values. Leave the seed blank when you want a fresh random batch for exploratory testing.
Choose profile when you need fuller menu data with dish, description, cuisine and ingredient fields together. Choose dish, ingredient, spice, fruit, vegetable or another field method when a form, table or import job only needs one value type.
Yes, use method=dish when you need dish-name fixtures, or method=profile when you want dish names alongside descriptions, cuisines and ingredients. The values are synthetic sample data for tests and prototypes.
Read the food data generator guide for endpoint options, response fields and integration patterns. The guide also shows where food data fits beside commerce, company, person and date generators.

​
Try it

Generate sample food data in the browser at spotzee.com/tools/food-generator, or call the Extended API when you need food fixtures inside automated tests and seed scripts.