Implement menu item 86 (out-of-stock) and restock updates on Uber Eats in real time using the Availability API
domain: developer.uber.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Verify Uber Direct webhook signatures — the full failure-mode walkthrough related to developer.uber.com, checked against official docs, with linked verified routes.
Steps
Obtain the Uber Eats store ID and the external item IDs as published in the live Uber Eats menu for the target location
When an item goes out of stock, call the item availability endpoint with the item's external ID and set availability to false or the out-of-stock status
Confirm the API response indicates the item is now hidden or marked unavailable on the storefront
When the item is restocked, call the same endpoint with availability set to true to reinstate the item
Automate this flow from POS inventory events or KDS alerts rather than relying on manual operator action to reduce lag
Known gotchas
The availability update applies to the specific store; if your menu item external IDs differ across stores, ensure you use the correct store-scoped external IDs
Item suspension does not remove the item from the menu permanently; a full menu republish will restore a suspended item if suspension state is not preserved in your system
High-frequency availability toggling (e.g. toggling an item dozens of times per hour) may trigger rate limiting — batch availability updates where possible
Give your agent this knowledge — and 15,800+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?