Integration · ezCater
ezCater API integration for restaurant catering
Get ezCater catering orders straight into your POS and kitchen, keep catering menus in sync and send delivery tracking back to ezCater, without re-keying orders from a tablet.
Takes two minutes. An engineer reads it, and Max replies within 1 business day.
- API
- GraphQL, signed webhooks
- Access
- Brand's API user in ezManage
- Sandbox
- None documented
- Market
- US
In short
An ezCater integration connects ezCater's catering marketplace to your POS, kitchen and delivery through the ezCater API, a GraphQL API: orders in, menus out, delivery tracking back. The brand creates an API user in ezManage and grants it the Integrations permission; order events arrive by signed webhook. Uber agreed to buy ezCater in October 2026, and the API hasn't changed yet. dev.family builds catering connectors for restaurant groups and runs them under an SLA.
What data moves
What an ezCater integration moves
Read means we can get it from ezCater. Write means we can send it to ezCater.
| Object | Read | Write | What the API supports |
|---|---|---|---|
| Orders | Yes | Partly | Order details by webhook; accept or reject through the API. An edit fires a new accepted event |
| Menus | No | Yes | Menu API pushes your catering menu to ezCater's catalog |
| Delivery tracking | No | Yes | Courier details, delivery events, location and drop-off photos |
| ezCater drivers | Yes | Yes | Request ezCater's third-party drivers for an order |
| Caterer locations | Yes | No | Bulk store setup isn't available through the API |
| Payouts and reviews | No | No | Not in the public API |
Common setups
How groups connect ezCater
Catering into the POS
ezCaterYour POSKitchenCatering orders print in the kitchen like any other order, with the right lead time.
Through Olo Rails
Brands on Olo can send ezCater orders to Toast or another POS through Rails.
Your drivers or theirs
Deliveries go to your courier setup or to ezCater's drivers, with tracking sent back.
API access
How ezCater API access works
Access is granted by the brand. A user in your ezManage account creates an API user, and a brand admin gives it the Integrations permission; that user's token signs every call. The Delivery API also needs a subscription to submitted orders first.
If you are building a brand-new integration, ezCater asks you to contact its API partnerships team before you start.
Docs catering.ezcater.io · checked November 9, 2026
What we need from you
- A brand admin in ezManage
- Which stores take catering orders
- How catering orders should reach the kitchen
- A real test store: there's no documented sandbox
Getting access:
an API user can be created in ezManage right away; a new integration starts with ezCater's partnerships team.
Platform limits
Where ezCater integrations break
No sandbox. ezCater documents no test environment, so test orders run against a real store. Plan who cancels them.
Edits look like new orders. There's no updated event: a changed order fires another accepted event. Your connector has to match it to the original and update the kitchen ticket.
No published limits or changelog. We found no rate limits and no dedicated changelog. Watch the product updates in the help center.
The Uber deal. Uber plans to bring ezCater onto Uber Eats and Uber for Business. When the deal closes, expect changes to accounts and possibly the API.
Run
Who fixes it when the platform changes its API
Monitoring
We check the connector against the live API every day and log every failed call.
Versions
We track the platform's changelog and move the connector to a new version before the old one is retired.
Alerts
Lost or stuck orders page the on-call engineer, who fixes them under the SLA.
Questions
Didn't find your answer? Ask on the call.
Yes. ezCater offers a GraphQL API with Orders, Menus and Delivery parts, documented in its catering help center. Order events such as accepted and canceled arrive by webhook with a signature header.
The brand creates an API user in ezManage, and a brand admin grants it the Integrations permission. New integration builders contact ezCater's API partnerships team before they start.
Read order details and caterer locations, accept or reject orders, push menus to ezCater's catalog, send delivery tracking with courier location and drop-off photos, and request ezCater's own third-party drivers. Bulk store setup isn't available through the API.
Not yet. Uber agreed on October 5, 2026 to buy ezCater for about $2.3 billion in cash and plans to bring it onto Uber Eats and Uber for Business. The deal was not closed when we checked on November 9, 2026. We'll update this page when the API changes.
Yes. ezCater marketplace, online ordering and meal program orders can flow through Olo Rails. An older ezCater FAQ mentioned an extra fee per order on that route; the current Rails page doesn't, so confirm it with ezCater.
Toast doesn't offer one directly: its help center lists ezCater among partners that aren't available through Toast Partner Integrations. ezCater orders reach Toast through a middle layer: Olo Rails, if your Toast locations already take Olo orders, or Deliverect, which integrates with both ezCater and Toast. The other route is a custom connector that reads accepted orders from the ezCater API and writes them to Toast through a custom integration for your locations.
ezCater publishes no timeline, and we found no sourced market estimate. There's no documented sandbox, so testing needs a real test store. We fix the price per scope before the build.
Get a scope estimate for your ezCater integration
Tell us how many stores take catering, which POS they run and how you deliver. An engineer will reply with what's possible and how long it takes.
a call with an engineer, then a fixed-price Integration Build. If the connector is part of a bigger change across brands, we start with a 2–3 week Assessment. How we work
Software vendor?We build connectors for food-tech products too, under your brand or ours. Restaurant API for software vendors
Max will reply within 1 business day with what's possible, what access we need and a rough timeline.