Meal Plan Settings Object
The meal plan settings object
Meal Plan Settings contain all the essential information based on which your meal plan is created. The Meal Plan API provides you with endpoints to Get and Update the settings as needed.
This is how the data structure of a Meal Plan settings
object looks like:
The following attributes define the core of the settings
object:
Attribute | Type | Description | Example Value |
| integer | The number of people to serve meals in the meal plan. |
|
| integer | The number of daily calories (with a ±100 kcal variance) that are expected to be served by the meal plan. |
|
| string | This attribute is deprecated and has been replaced by the | _ |
| string | This attribute is deprecated and has been replaced by the | _ |
| boolean | Agreement to generate the meal plan automatically. This attribute has no impact on the auto-generation algorithm irrespective of its value. |
|
| array | The schedule settings of the meal plan. It includes information on preferred days and slots for meals assignment. | See |
| boolean | Controls the replacement of manually added meals with new auto-generated meals in the meal plan. |
|
| string | The starting day of the week in the meal plan schedule. |
|
| string | The meal generation algorithm. |
|
| array | User's preferences related settings for filtering recipes. | See |
| array | A list of labels for filtering recipes. | See |
Each array contains additional attributes as described below.
week_template
week_template
Attribute | Type | Description | Example Value |
| string | Represents a day of the week. |
|
| array | Includes mapping details of different meal-types with day slots, which means what type of meals should be generated to which slot in a day. For more information, see the array break-up below. |
|
The meal_templates
array contains the following attributes:
Attribute | Type | Description | Example Value |
| string | The different types of meal that you may have during the day. These meal-types are independent of day slots and can be assigned to any day slot as required. Additionally, the meal-types are also independent of recipe labels, which means you can have a meal-type as Lunch but inside it, you can use a Breakfast recipe for the meal. |
|
| integer | Indicates a slot within the day to consume a meal. As part of your meal plan, you can as many as 7 slots in a day dedicated to different meal-types. |
|
food_settings
food_settings
Attribute | Type | Description | Example Value |
| array | Labels specific to the user's preferences for filtering recipes. For more information, see the array break-up below. |
|
| array | Includes information on any specific ingredients and the number of ingredients to be considered for filtering recipes for the meal plan. For more information, see the array break-up below. |
|
| array | Includes the minimum health score to be considered for filtering recipes for the meal plan. Health Scores are calculated on a 2 to 10 scale based on nutrient density and USDA recommendations for a healthy diet. A higher Health Score means healthier food. For more information, see Heath Score. |
|
The labels
array contains the following attributes:
Attribute | Type | Description | Example Value |
| array | A list of labels of different categories. For more information, see Labels. |
|
| boolean | Controls the filtering approach. |
|
The include_ingredients
array contains the following attributes:
Attribute | Type | Description | Example Value |
| string | A name of a particular ingredient to match while filtering recipes. |
|
| integer | Indicates the minimum number of ingredients that must match while filtering recipes.
If the value specified is greater than |
|
custom_labels
custom_labels
Note: These labels are generally created in the Whisk Studio application and are left blank while managing meal plan settings using the Whisk API.
To learn how to pull or update meal plan settings, read the following endpoints' documentation:
Get Meal Plan SettingsUpdate Meal Plan SettingsLast updated