restrict uber eats menu items to specific hours and temporarily suspend out-of-stock items using visibility_info and suspension_info
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
Use the Menu API's visibility_info fields on a menu item to define the hours/days during which that item is orderable (dayparting)
Use suspension_info with a suspend_until timestamp and a reason to temporarily pull an item from sale (e.g., unexpected 86)
Push the updated menu via the Menu API POST endpoint and confirm the change is reflected in the Get Menu API response
Let suspension clear automatically at suspend_until, or explicitly update the item again to lift suspension early
Validate that item-level visibility rules only apply when the item is used as a standalone/parent item, not as a modifier option
Known gotchas
visibility_info hour restrictions only take effect on parent/standalone items — modifier options inherit the parent item's visibility and cannot be independently restricted to different hours
suspension_info requires both a suspend_until timestamp and a reason; omitting either can cause the Menu API to reject the update
Suspending an item doesn't remove it from the menu structure — it remains defined but unorderable, so downstream systems that only check "item exists" rather than suspension state will still treat it as available
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ 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?