Configure an Uber Direct catering delivery with inside setup and photo-verified proof of delivery
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
Request a delivery quote via the Uber Direct API and create the delivery, including manifest_items describing each tray/item and any item_customizations
Set the dropoff instructions/options to request the courier bring the order inside and perform minimal unpacking/setup at the dropoff address, per Uber's catering delivery support flow
Schedule the delivery for the event's required arrival window if it isn't an immediate dispatch
After setup, confirm the delivery-completed webhook includes the proof-of-delivery photo taken to verify the catering setup
Handle SCHEDULED-to-COMPLETED status transitions via the delivery status webhook rather than polling
Known gotchas
Inside setup is a customer-requested service tier for catering drop-offs, not the default Uber Direct dropoff behavior - it must be explicitly configured/requested per delivery
Always verify webhook signatures on delivery status callbacks before trusting the payload, including the proof-of-delivery photo reference
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?