> For the complete documentation index, see [llms.txt](https://mobile-calendar.gitbook.io/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mobile-calendar.gitbook.io/v1/dictionaries/meals.md).

# Meals

This document lists **static meal plan codes** used by the Mobile Calendar API.\
These values are used in reservations, room rates, and pricing configurations.

* **id**: Internal identifier (integer)
* **code**: Short code used in PMS/channel manager integrations
* **description**: Full name or meaning of the meal plan

{% hint style="info" %}
**Note:** This is a static reference list. Use these codes when specifying or interpreting meal plan types.
{% endhint %}

## Table

| id | code | description                 |
| -- | ---- | --------------------------- |
| 0  | OV   | No meals                    |
| 1  | BB   | Breakfast                   |
| 2  | HB   | Breakfast and lunch         |
| 3  | FB   | Breakfast, lunch and dinner |
| 4  | AI   | All inclusive               |
| 5  | —    | Lunch                       |
| 6  | —    | Breakfast and dinner        |
| 7  | —    | Lunch and dinner            |
| 8  | —    | Dinner                      |

***

## Usage Notes

* Used primarily in **reservations** and **rate plans** endpoints.
* The **code** is the industry-standard short label (where applicable).
* When saving data, always pass the **id** (integer) to the API.
* Non-standard plans without code (`—`) are for internal or extended use.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://mobile-calendar.gitbook.io/v1/dictionaries/meals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.