process uber direct batched deliveries using batch_id, dropoff_sequence_number, and short_batch_id
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
Create deliveries as normal via the Uber Direct create delivery endpoint
Monitor delivery status webhooks and get-delivery responses for the batch_id field, which replaced the older route_id for identifying batched orders
Use dropoff_sequence_number to determine the order in which a courier will complete multiple drops within the same batch
Display or reference short_batch_id in courier-facing or customer-facing surfaces since it is the compact human-readable identifier for the batch
Reconcile per-delivery status independently even when deliveries share a batch, since each dropoff completes and reports status separately
Known gotchas
Treating batch_id as a synonym for the deprecated route_id will break integrations built before Uber's field migration
dropoff_sequence_number can change if Uber's routing re-optimizes the batch mid-route, so don't cache it as immutable
Not all Uber Direct deliveries are batched; code must handle the absence of batch fields gracefully for single-drop deliveries
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?