30 lines
1.3 KiB
Markdown
30 lines
1.3 KiB
Markdown
# 05 Menu Example Payloads (v2)
|
|
|
|
These files are curated from the Uber v2 menu examples you shared, cleaned into valid JSON and ready for direct use in this wrapper.
|
|
|
|
Use with:
|
|
|
|
- Upload menu: `PUT /api/v1/uber/menu/replace`
|
|
- Update one item (sparse): `POST /api/v1/uber/menu/items`
|
|
|
|
## Files
|
|
|
|
- `docs/examples/menus/v2/empty-menu.json`
|
|
- Empty menu payload (can clear existing menu)
|
|
- `docs/examples/menus/v2/simple-menu.json`
|
|
- Simple menu with categories, items, and modifier groups
|
|
- `docs/examples/menus/v2/fulfillment-delivery-menu.json`
|
|
- Delivery-specific menu (`menu_type = MENU_TYPE_FULFILLMENT_DELIVERY`)
|
|
- `docs/examples/menus/v2/fulfillment-pickup-menu.json`
|
|
- Pickup-specific menu (`menu_type = MENU_TYPE_FULFILLMENT_PICK_UP`)
|
|
- `docs/examples/menus/v2/combo-bundled-items.json`
|
|
- Combo example with `bundled_items` + `core_price`
|
|
- `docs/examples/menus/v2/update-item-sparse.json`
|
|
- Sparse item update for `POST /v2/eats/stores/{store_id}/menus/items/{item_id}`
|
|
|
|
## Practical Notes
|
|
|
|
- For split fulfillment menus, upload `DELIVERY` first; after split, manage each menu type separately.
|
|
- Keep item IDs stable and avoid problematic characters like `/` and `;`.
|
|
- `alcoholic_items > 0` behaves as sticky in Uber and cannot be reverted by normal API update.
|