In ezManage, create a technical integration user under Settings > Users & Permissions and assign it the Integrations permission for the relevant store locations to enable token generation.
Authenticate using the credentials associated with the technical user to obtain an API token for subsequent requests.
Construct the catering menu payload following ezCater's menu schema, including categories, items, modifiers, prices, and minimum order quantities appropriate for catering.
Submit the menu to ezCater via the Menus API endpoint; ezCater validates the payload and maps it to the restaurant's storefront.
Subscribe to the menu sync webhook to receive confirmation of successful publication or validation error details.
Update the menu via the same API whenever prices, availability, or item descriptions change in the source POS or menu management system.
Known gotchas
ezCater catering menus have different structural requirements than standard delivery menus — minimum order quantities, lead times, and headcount fields are required; a standard POS menu export will typically need transformation before submission.
The ezCater Menu API launched publicly in early 2025; earlier integrations may have used manual CSV import or portal-based updates — verify you are using the current API version rather than legacy documentation.
API token generation requires a technical user configured in ezManage with explicit Integrations permission per location; missing this permission results in authentication failures that are not clearly described in the error response.
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