API Reference

Nutrients, Brands & Categories

Paginated reference endpoints expose the taxonomy behind the food catalog. Use them to build filter dropdowns, map your own nutrition models, or validate data coming from search. Authenticated catalog lists: /api/v1/catalog/brands|categories|nutrients. Public demos (no key, IP limited): /api/v1/public/catalog/brands|categories|nutrients.

Nutrients

List the nutrient definitions used in food payloads, macronutrients, vitamins, and minerals with their units.

curl "https://calorieapiadmin.com/api/v1/catalog/nutrients" \
  -H "X-API-Key: your_api_key_here" \
  -G -d "limit=50" -d "skip=0"

Brands

Browse brand records referenced by branded foods. Combine with the brand filter on food search to scope results to a manufacturer.

curl "https://calorieapiadmin.com/api/v1/catalog/brands" \
  -H "X-API-Key: your_api_key_here" \
  -G -d "limit=100" -d "skip=0"

Categories

Access food categories and subcategories for organizing and filtering foods in your UI.

curl "https://calorieapiadmin.com/api/v1/catalog/categories" \
  -H "X-API-Key: your_api_key_here" \
  -G -d "limit=50" -d "skip=0"

Query parameters (all three endpoints)

limitResults per page, 1–1000 (default: 100)

skipOffset for pagination (default: 0)

searchOptional name filter (min 2 characters). q is accepted as an alias.

All three return the standard paginated envelope (data, total, skip, limit). Reference data changes rarely, so it is a good candidate for caching in your application.

Frequently asked questions

How often does reference data change?

Rarely; nutrients, brands, and categories evolve with catalog updates but are stable enough to cache for a day or longer in your application.

Can I search brands by name?

Yes. Add search={name} (min 2 characters) to GET /api/v1/catalog/brands to name-filter the list. GET /api/v1/search/brands?q={name} also performs a brand name search.