NutritionSignals API Documentation
NutritionSignals resolves food inputs into clean, normalized nutrition data. Submit barcodes, nutrition labels, or text descriptions and receive structured macros, ingredients, and serving sizes without building or maintaining food infrastructure.
Getting started
To get started, generate an API key in your developer settings. Your first request will use the Food Resolution endpoint, which accepts partial or messy food inputs such as a barcode, nutrition label image, or text description and returns normalized nutrition data when available.
NutritionSignals is designed to be resilient to incomplete data. When exact matches aren’t available, the API applies normalization and fallback logic to return the most useful structured result possible, along with confidence and source metadata.
Resources
Food Resolution
Resolve messy food inputs (text, barcode, label text) into normalized macros, ingredients, serving sizes, and confidence metadata.
Authentication
Learn how to authenticate with your API key, rotate keys safely, and keep requests secure across environments.
Errors & Confidence
Understand error codes, “not found” cases, and how to use confidence and source fields to build reliable UX.
Rate limits
See request limits, recommended retry behavior, and how usage scales as you grow on NutritionSignals.