# Meal Plan Management

## Create Meal Plan

Calling any one of the Meal Planner API endpoints will first check whether the user has a meal plan assigned to them. If they do not, the meal plan will be automatically created for them. This means that the developer is not required to actively create a meal plan for the user.

## The Meal Plan ID

Our [API spec](https://api.whisk.com/spec/#/MealPlanAPI) clearly shows that each endpoint has two versions - one with `meal_plan_id` and one without.

For example:

| GET | `/mealplan/v2/meal` |
| --- | ------------------- |

and

| GET | `/mealplan/v2/:meal_plan_id/meal` |
| --- | --------------------------------- |

The `meal_plan_id` section is optional - the endpoint will return the same result whether it is provided or not.

This is because Whisk supports a single meal plan for each user at this time. Multiple meal plans will be supported in future versions. Therefore, the `meal_plan_id` will be directly derived from the user’s ID. The user ID is extracted using the OAuth token provided with each endpoint header, as described above.

## Get Meal Schedule

| GET | `/mealplan/v2/meal` |
| --- | ------------------- |

This endpoint gets a list of meals for a specified time period. For more information, follow this link:<https://api.whisk.com/spec/#/MealPlanAPI/GetMealSchedule2>.

## Manage Meal

### Add Meal

| POST | `/mealplan/v2/meal` |
| ---- | ------------------- |

API spec: <https://api.whisk.com/spec/#/MealPlanAPI/AddMeal2>

### Update Meal

| PUT | `/mealplan/v2/meal/:meal_id` |
| --- | ---------------------------- |

API spec: <https://api.whisk.com/spec/#/MealPlanAPI/UpdateMeal2>

### Delete Meal from Meal Plan

Removes a single meal from a specified meal plan.

## Delete Meal from Meal Plan

<mark style="color:red;">`DELETE`</mark> `https://graph.whisk.com/mealplan/v2/meal/:meal_id`

#### Path Parameters

| Name     | Type   | Description         |
| -------- | ------ | ------------------- |
| meal\_id | string | The meal identifier |

#### Request Body

| Name           | Type   | Description              |
| -------------- | ------ | ------------------------ |
| meal\_plan\_id | string | The meal plan identifier |

{% tabs %}
{% tab title="200 Upon successful deletion, the method returns an empty object." %}

```javascript
{}
```

{% endtab %}
{% endtabs %}

API spec: <https://api.whisk.com/spec/#/MealPlanAPI/DeleteMeal2>

### Conflicts resolution

The `on_conflict` field allows meals to either replace or be inserted into daily meal slots when using the **Add Meal** or **Update Meal** endpoints. This helps the meal planner avoid any conflicting actions in case of adding or updating a meal into a daily slot which already is populated with a pre-existing meal.

Here are the following options for the `on_conflict` field:

* `DAY_SLOT_CONFLICT_ACTION_REPLACE` - the new meal will replace the existing one. **This is the default option.**
* `DAY_SLOT_CONFLICT_ACTION_INSERT` - the new meal will be inserted before the existing one, pushing it, along with all following meals, forward one daily slot. However, if you exceed the maximum number of daily meals (7), a 400 error response will be returned.
* `DAY_SLOT_CONFLICT_ACTION_FAIL` - the new meal will not be inserted into the daily slot, and a 400 error will be returned.

### Get Meal Plan Recipes

To get the recipes for the meal plan just use the recipe search endpoint:

| POST | `/recipe/v2/search` |
| ---- | ------------------- |

More info here: <https://api.whisk.com/spec/#/RecipeAPI/SearchRecipes>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.whisk.com/master/api/meal-plans/meal-plan-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.