Menus

Keep menus, hours, and item availability in sync when Otter pushes changes to your integrated service.

Overview

Use this when Otter is the source of menu changes and your app applies them on a marketplace, POS, or other target. Otter sends webhook events; you perform the operation on the target and report results via callback endpoints.

How it fits

Integration overview

1. Receive a menu-related webhook (publish, hours, availability, or send menu).
2. Apply the change on the integrated service.
3. POST the result to the matching callback endpoint — or report a failure.

Flow	Webhook intent	Callback
Publish a menu	Menu Publish (menus.menu_publish)	POST /v1/menus/publish
Upsert hours	Menu upsert hours (menus.upsert_hours)	POST /v1/menus/hours
Update availability	Update menu entities availabilities (menus.update_menu_entities_availabilities)	POST /v1/menus/entity/availability/bulk
Send menu	Send menu (menus.send_menu)	POST /v1/menus/current

Test

• Register webhooks and validate signatures.
• Walk through Publish a menu with a test store.

Related

• Menus Manager — when your app owns the menu catalog
• API reference

Next

Start with Publish a menu. Before go-live, confirm error reporting via Handle failed events.