Register your order webhook endpoint in ezManage or via the public API for catering partners; ezCater supports webhook subscriptions for order lifecycle events.
When an order is placed, ezCater POSTs an order event payload to your endpoint containing order details, line items, delivery address, headcount, and requested delivery time.
Respond with HTTP 200 immediately to acknowledge receipt; ezCater retries delivery on non-2xx responses.
Parse and normalize the ezCater order schema into your POS or kitchen management system format, paying attention to catering-specific fields like headcount and requested serving time.
Use the delivery public API to push delivery status updates (accepted, preparing, dispatched) back to ezCater so the platform can keep the customer informed.
For cancellations or modifications, handle the corresponding webhook event types and update your internal order records accordingly.
Known gotchas
ezCater orders are typically placed with significant lead time (hours to days); ensure your system does not treat catering orders like on-demand orders and trigger immediate kitchen prep on receipt.
The ezCater Delivery Public API and the Catering Partners API are separate products with different authentication and endpoint structures — confirm which API your integration scenario maps to before building.
ezCater integration access is granted via the partner program; direct API access is not available without completing the partner onboarding process.
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