# Menu changed event

Sent when a location's menu is modified. Re-fetch the full menu
via GET /locations/{location_id}/menu. Use version_hash to
avoid unnecessary re-fetches.

Endpoint: POST menu-changed
Version: 1.0.0
Security: 

## Request fields (application/json):

  - `event_id` (string, required)
    Unique identifier for this event. Use for idempotent processing.

  - `event_type` (string, required)
    The type of event that occurred. Determines the shape of the data field.

  - `created_at` (string, required)
    When the event occurred (ISO 8601 UTC).

  - `data` (object, required)
    Event-specific payload. Shape depends on event_type.
See individual event schemas for details.

  - `data.location_id` (string, required)
    The location whose menu changed.

  - `data.version_hash` (string, required)
    New menu version hash. Compare with your cached version to
determine if a re-fetch is needed. Matches the version_hash
field from GET /locations/{location_id}/menu/metadata.
    Example: "sha256:b2c3d4e5f6a7"

  - `data.change_type` (string, required)
    The type of menu change that occurred.

- ITEMS_ADDED: New items added to the menu.
- ITEMS_REMOVED: Items removed from the menu.
- ITEMS_MODIFIED: Existing items changed (price, name, modifiers, etc.).
- CATEGORIES_CHANGED: Category structure modified (added, removed, reordered).
- FULL_UPDATE: Bulk menu update affecting multiple aspects.
    Enum: "ITEMS_ADDED", "ITEMS_REMOVED", "ITEMS_MODIFIED", "CATEGORIES_CHANGED", "FULL_UPDATE"

  - `data.changed_at` (string, required)
    When the menu change occurred.


## Response 200 fields