Codex-oriented nutrition label for one food
GET /foods/{id}/label · API key required
Standardized nutrition label built from Serving-Size Intelligence. References CXS 1-1985 (General Standard for the Labelling of Pre-packaged Foods) and CXG 2-1985 (Guidelines on Nutrition Labelling) separately as `labelling_standard` and `nutrition_labelling_guideline`. Every nutrition_declaration and vitamins_minerals_detail field carries an explicit status — `available`, `not_available`, or `estimated` — so a genuine 0 is never rendered the same as missing data, and `estimated` only appears where the source FCT's own data_quality_flags marks that value as assumed. `per_100g_reference` exposes the raw per-100g basis a scaled serving was derived from. Defaults to the most specific local serving available (chipande/mtanda, cup, tablespoon, handful, piece, etc.); an unrecognized `?serving=` falls back to the default rather than erroring, flagged via `requested_serving.matched=false`. All existing response fields (serving_size, calories, total_fat_g, saturated_fat_g, carbohydrates_g, fiber_g, sugars_g, protein_g, sodium_mg, vitamins_minerals, standard, missing_fields) are unchanged.
Parameters
id(path, required)serving(query) - Case-insensitive substring match against a serving_sizes label (e.g. "chipande", "mtanda", "100g", "cup"). Omit to get the most specific serving Serving-Size Intelligence has for this food. An unmatched value falls back to the default and…
Responses
200- Nutrition label built successfully400404422- No serving-size data available, or an invalid (non-positive) serving weight