Routes & Descriptions
Last updated
Last updated
Given a product code, such as 698241110109
from UPC/Barcode scanning, get the detailed information and nutrients of the corresponding food product.
Given a food items ID, such as 698241110109
get the detailed information and nutrients of the corresponding food product.
All items returned from our API come with a Reference Code. This can be used to retreive the same item later, and to store custom data if necessary.
This route allows text search against our entire database of foods, products, and recipes.
Simply URL Encode your search term to take care of special characters, and send the request! The default limit (max results returned) is 50. This is the recommended setting, but can be adjusted as needed.
labelId
If the selected result has a labelId, pass it as this parameter.
If the labelId is empty, pass an all 0's uuid:
00000000-0000-0000-0000-000000000000
type
All search results will have a type
field which will be one of synonym, recipe, or reference. Pass this value to the type parameter
resultId
all search results will have a resultId
. Pass this value to the resultId parameter
This route remains to support backward compatibility. should be used instead for all new implementations.
get food record by its corresponding food identifier
food id (ex: 1599690204479)
client can send additional key/value pair data where keys are strings, and values are some json-serializable type. The data should be JSON-encoded and then base64-URL encoded
given a search result refcode, retreive the full food information
the string of a base64 url encoded json str. returned with results as 'refCode' from this api. example decoded object: {\
client can send additional key/value pair data where keys are strings, and values are some json-serializable type. The data should be JSON-encoded and then base64-URL encoded
search for food (generic, branded or restaraunt) or recipes
enter your search term here.
sets the maximum number of results to be returned; narrowing, if applied, occurs after this limit.
client can send additional key/value pair data where keys are strings, and values are some json-serializable type. The data should be JSON-encoded and then base64-URL encoded
set to true to enable a more intelligent AI than default to sort the results. This mode will cost more tokens when enabled, and be slightly slower to respond.
given a search result object, retreive the full food information
labelid from search result. use an all zeros uuid if unknown.
type from search result
resultid from search result
client can send additional key/value pair data where keys are strings, and values are some json-serializable type. The data should be JSON-encoded and then base64-URL encoded