UBER-EATS-Wrapper/docs/developer-portal/06-order-api-1-0-0-audit.md

06 Order API 1.0.0 Audit

Source checked: "Order Fulfillment API (1.0.0)" shared by you.

Implemented Now (Dedicated Wrapper Namespace)

• Get Order Details:
  • GET /api/v1/uber/delivery-order/orders/{orderId}
  • upstream: /v1/delivery/order/{order_id}
• List Orders Details:
  • GET /api/v1/uber/delivery-order/stores/{storeId}/orders
  • upstream: /v1/delivery/store/{store_id}/orders
• Accept Order:
  • POST /api/v1/uber/delivery-order/orders/{orderId}/accept
• Deny Order:
  • POST /api/v1/uber/delivery-order/orders/{orderId}/deny
• Cancel Order:
  • POST /api/v1/uber/delivery-order/orders/{orderId}/cancel
• Mark Order Ready:
  • POST /api/v1/uber/delivery-order/orders/{orderId}/ready
• Adjust Order Price:
  • POST /api/v1/uber/delivery-order/orders/{orderId}/adjust-price
• Update Order Ready Time:
  • POST /api/v1/uber/delivery-order/orders/{orderId}/update-ready-time
• Resolve Fulfillment Issues:
  • POST /api/v1/uber/delivery-order/orders/{orderId}/resolve-fulfillment-issues
• Get Replacement Recommendations:
  • POST /api/v1/uber/delivery-order/replacement-recommendations

Validation Added

• adjust-price reasons enum and custom_reason required when reason is OTHER
• update-ready-time requires ready_for_pickup_time
• deny/cancel reason object shape validation
• list orders page size max enforced (<= 50)

Existing Before

• Legacy order routes under /api/v1/uber/orders...
• Retail fulfillment helpers and related webhooks

Pending

• Response normalization nuances for 204 No Content cancel semantics if required by consuming clients
• Deeper typed schemas for webhook metadata and fulfillment issue object variants