Create an API user in the ezCater partner portal and complete the invitation flow to set a password and generate your authorization token
Review the ezCater menu data model: menus are structured as categories (sections) containing items, with items having options and choices; map your POS menu hierarchy to this structure before building the sync
Build a menu payload conforming to the ezCater Menus API specification, including category names, item names, descriptions, prices, and modifier options; validate required fields against the API documentation
Push the menu payload to the Menus API endpoint; the API supports both initial menu creation and subsequent updates — use the appropriate endpoint or method for each scenario
Subscribe to order webhooks so your POS or order management system receives catering orders placed through ezCater; acknowledge each webhook promptly to confirm receipt
Implement a menu-sync trigger in your POS integration so that item price changes or 86'd items (marked unavailable) automatically push a delta update to ezCater within a defined SLA
Known gotchas
ezCater's menu API was launched publicly in February 2025 — if you integrated via an older manual or CSV menu submission process, migration to the API may require re-mapping your menu structure to the category/item/option/choice hierarchy
Catering menus often include lead-time and minimum-order constraints that standard delivery menus do not — ensure these catering-specific attributes (e.g., minimum order value, advance notice hours) are included in your menu payload where the API supports them
Authorization tokens in the ezCater API are generated per user session after password setup; automate token acquisition in your integration to avoid expired-token failures during scheduled menu syncs
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp