Food Information API by Edamam is here to offer quality and accurate elements required to have in culinary applications, websites and blogs, website plugins, product marketing and more use cases. Get connected to the Food Information API provider to receive precise data for searching for nutrition and diet information within Edamam’s Food Database and similar objectives right away.
Menu
Nutrition Analysis API
Nutrition analysis API for fetching the nutritional information based on a POST request of the recipe content
Get access to the data made by Edamam and use this nutrition analysis API with the goal of fetching the nutritional information based on a POST request of the recipe content. The data is used by small business, medium business and enterprises, the customers use the API within the culinary, social media, food and grocery, restaurant and more sector. A few examples of the type of business that uses the API are culinary and hobby websites, cooking app and platform developers, influencers, online shopping platforms, marketers and more. When filtering the API based on the app_id, app_key, beta, If-None-Match, force and body you will be able to get the output which you need for your system. This database covers global data. There are endless systems which are being built using the nutrition analysis data. Developers continue to come up with new ideas for using the API, here we have some potential cases; culinary applications, websites and blogs, website plugins, product marketing and more and certainly there are much more you can think of.
Menu
Nutrition Analysis API endpoints
| POST |
| GET |
| /api/nutrition-details |
| /api/nutrition-data |
| POST | /api/nutrition-details |
| GET | /api/nutrition-data |
To be able to use this platform for fetching the nutritional information based on a POST request of the recipe content, customers should connect to the API endpoint; /api/nutrition-details to obtain a similar response as in the example data output. Input the API endpoint into the URL to execute the request. The object and description table demonstrates the applicable parameters and objects output explanations. All major coding languages work with the data output. Customers just need to attach the private API key as an endpoint parameter and customers will start receiving data.
API parameters for nutrition analysis data
The nutrition analysis API has the below mentioned filtering parameters applicable to use.
| Filters | ||
app_id |
body |
|
app_key |
|
|
beta |
|
|
If-None-Match |
|
|
force |
|
API object attributes
Obtain the requested data from the system using the parameters applicable and the table to interpret the objects.
| Objects | Description |
post | |
tags | |
summary | |
description | |
consumes | |
parameters | |
name | |
in | |
x-data-threescale-name | |
description | |
required | |
type |
Output response of nutrition analysis API
Here is an example data response of the endpoint call. There is more data available, it is limited to be able to make it readable. Subscribe for the API and gain access to the complete output response.
{
"swagger": "2.0",
"info": {
"version": "1.1",
"title": "",
"description": ""
},
"schemes": [
"https"
],
"host": "api.edamam.com",
"tags": [
{
"name": "Individual Text Line Analysis"
},
{
"name": "Full Recipe Analysis"
}
],
"paths": {
"/api/nutrition-details": {
"post": {
"tags": [
"Full Recipe Analysis"
],
"summary": "<b>Click here to view the documentation</b>",
"description": "This returns the nutritional information based on a POST request of the recipe content. The POST request submits the recipe content, specifically the recipe title and ingredient list. The response the API returns, will contain the nutritional analysis for the recipe based on the information provided. <b>Access Point:</b> https://api.edamam.com/api/nutrition-details",
"consumes": [
"application/json"
],
"parameters": [
{
"name": "app_id",
"in": "query",
"x-data-threescale-name": "app_ids",
"description": "App ID from your dashboard",
"required": true,
"type": "string"
},
{
"name": "app_key",
"in": "query",
"x-data-threescale-name": "app_keys",
"description": "App key from your dashboard",
"required": true,
"type": "string"
},
{
"name": "beta",
"in": "query",
"description": "Allow beta features in the request and response",
"type": "boolean"
},
{
"name": "If-None-Match",
"in": "header",
"description": "Each successfully processed recipe will also return a tag in the ETag response header. This value must be preserved together with the recipe. When resubmitting the recipe, you should include the value in the If-None-Match request header and store the updated ETag header.",
"type": "string"
},
{
"name": "force",
"in": "query",
"description": "Forces the re-evaluation of the recipe. The value, if any, is ignored.",
"type": "boolean"
},
{
"name": "body",
"in": "body",
"description": "Using the food ID and the measure URI which parser provides you can make a request to the nutrients access point. The nutrients access points returns nutrition with diet and health labels for a given quantity of the food.",
"required": true,
"schema": {
"type": "object",
"required": [
"title",
"ingr"
],
"properties": {
"title": {
"type": "string"
},
"ingr": {
"type": "array",
"items": {
"type": "string"
}
},
"url": {
"type": "string"
},
"summary": {
"type": "string"
},
"yield": {
"type": "string"
},
"time": {
"type": "string"
},
"img": {
"type": "string"
},
"prep": {
"type": "string"
}
}
}
}
],
"responses": {
"200": {
"description": "OK - Recipe object containing number of servings (yield), total calories for the recipe (calories), nutrient content by nutrient type (totalNutrients, totalDaily), diet and health classification (dietLabels, healthLabels)"
},
"304": {
"description": "Not Modified."
},
"404": {
"description": "Not Found - The specified URL was not found or couldn't be retrieved"
},
"409": {
"description": "The provided ETag token does not match the input data"
},
"422": {
"description": "Unprocessable Entity - Couldn't parse the recipe or extract the nutritional info"
},
"555": {
"description": "Recipe with insufficient quality to process correctly"
}
}
}
},
"/api/nutrition-data": {
"get": {
"tags": [
"Individual Text Line Analysis"
],
"summary": "<b>Click here to view the documentation</b>",
"description": "This returns the nutritional analysis for the specified food text by extracting information from a short unstructured food text (usually an ingredient line and returns the following structured data for the text: quantity, measure and food,) and if available: diet, health and allergen labels for the text. With the built in food logging feature, this allows for change of context. For example, “rice” will normally be matched to raw rice while, with the food logging feature on, it will match to ready to eat ‘cooked rice.’ <b>Access Point:</b> https://api.edamam.com/api/nutrition-data",
"parameters": [
{
"name": "app_id",
"in": "query",
"x-data-threescale-name": "app_ids",
"description": "App ID from your dashboard.",
"required": true,
"type": "string"
},
{
"name": "app_key",
"in": "query",
"x-data-threescale-name": "app_keys",
"description": "App key from your dashboard.",
"required": true,
"type": "string"
},
{
"name": "nutrition-type",
"in": "query",
"description": "Select between the cooking and food logging processor.",
"type": "string",
"default": "cooking",
"enum": [
"cooking",
"logging"
]
},
{
"name": "ingr",
"in": "query",
"description": "The ingredient.",
"required": true,
"type": "string"
},
{
"name": "If-None-Match",
"in": "header",
"description": "First, each successfully processed recipe will also return a tag in the ETag response header. This value must be preserved together with the recipe. Then, when resubmitting the recipe, you should include the value in the 'If-None-Match' request header.",
"type": "string"
}
],
"responses": {
"200": {
"description": "OK - Recipe object containing: number of servings (yield), total calories for the recipe (calories), nutrient content by nutrient type (totalNutrients, totalDaily), and diet and health classifications (dietLabels, healthLabels)"
},
"304": {
"description": "Not Modified"
},
"404": {
"description": "Not Found - The specified URL was not found or couldn't be retrieved"
},
"409": {
"description": "The provided ETag token does not match the input data"
},
"422": {
"description": "Unprocessable Entity - Couldn't parse the recipe or extract the nutritional info"
},
"555": {
"description": "Recipe with insufficient quality to process correctly"
}
}
}
}
}
}
SDK
There are SDKs accessible to help the development of your platform, simply email for them and they should be sent. Next use the filter attributes to filter the required output for you and with the recipe nutrition API response in JSON your project is clear to develop.
Nutrition Analysis API pricing
Before determining to buy API access you may ask for trials and samples of the nutrition analysis data. Email to inquire into the trial access and you will be able to experiment with the API. It will not be unlimited access but it is sufficient to test the API platform.
Price and cost of API
The API developed by Edamam is accessible monthly from $49 with secure payment and immediate access to get data.
| Option | Price |
Monthly subscription | From $49/month |
Variable pricing | no |
Free Trial
Free trial is available
Alternative options
Contact the Search Recipes By Nutrients API provider to access comprehensive data for finding a set of recipes that adhere to the given nutritional limits purposes today. Search Recipes By Nutrients API by Spoonacular offers extensive and fundemental elements necessary to have in culinary applications, websites and blogs, website plugins, product marketing and more fields.
Similar Recipes API ensures you get the best external data solutions to build products for finding recipes which are similar to the given one functions. The similar recipes API is the ideal data tool to directly get Food data to your project.
Ingredient Information API by Spoonacular offers extensive and necessary details necessary to have in culinary applications, websites and blogs, website plugins, product marketing and more related projects. Ingredient Information API proposes to offer precise culinary applications, websites and blogs, website plugins, product marketing and more data for building iOS and Android apps, online services, tools, software, market inquiries and much more.
Search Grocery Products API offers external data solutions to build data-oriented products for searching packaged food products, such as frozen pizza or Greek yogurt use cases. The search grocery products API is the ideal tool to directly get Food data to your client.
Menu Item Information API ensures you get the best external data solutions to develop projects for getting all available information about a menu item, such as nutrition objectives. Food data via menu item information API returns required details to ensure you can build advanced apps, websites, and more.
Menu
