Meal Plan
This is how the data structure of a Meal Plan object looks like:
The following attributes store the core information of a meal plan:
Attribute | Type | Description | Example Value |
| string | The meal plan identifier. |
|
| array | The start date of the meal plan. | See |
| array | The end date of the meal plan. | See |
| array | The information on different meals included in the plan. | See |
| string | The meal plan generation result code. |
|
Each array further contains additional attributes as described below.
start_date
/end_date
start_date
/end_date
Attribute | Type | Description | Example Value |
| integer | The year. |
|
| integer | The month. |
|
| integer | The day of the month. |
|
meals
meals
Attribute | Type | Description | Example Value |
| string | The meal identifier. |
|
| string | A label to identify the type of meal. |
|
| array | This attribute is deprecated and displays the same value as the | - |
| array | Contains the recipe data for the meal. | See Recipe Data. |
| boolean | Shows whether the meal is auto-generated or has been manually added by the user to the meal plan. |
|
| number | The day slot assigned to the meal. Each day consists of up to 7 slots, each containing a single meal along with its recipe information. |
|
| array | The date assigned to the meal. |
|
The Meal Plan API provides the following endpoints:
Note: All Meal Plan API endpoints first check whether a meal plan is already assigned to the user. When not found, a meal plan gets created and assigned to the user automatically. This means there is no need to manually create a meal plan for the user.
Last updated