{"id":"0a0df94f-e8a9-469d-8806-9773314a84bd","task":"Create a batched, multi-dropoff delivery with Uber Direct and correctly interpret dropoff_sequence_number and batch identifiers in status webhooks","domain":"developer.uber.com","steps":["Build the manifest for each order with item-level fields such as name, quantity, size, price, and dimensions/weight as required by the Create Delivery request","For orders that should be batched with a courier's existing route, use Uber Direct's batching support rather than issuing fully independent deliveries","Read dropoff_sequence_number from the Get Delivery response and delivery status webhook to determine each stop's position in the courier's route","Use the batch identifier returned on batched deliveries (rather than assuming a single delivery id maps 1:1 to a courier trip) when correlating webhook events back to orders","Test with sandbox/simulated couriers before relying on batch-specific fields in production, since batching behavior has changed across API versions"],"gotchas":["Batch-related fields (like short batch identifiers) have been added and renamed across Uber Direct API versions — pin to a changelog-verified field name rather than assuming older docs still apply","Not every delivery is eligible for batching; a request can silently return as a single, non-batched delivery if conditions aren't met","Manifest weight/dimension fields matter for courier vehicle assignment — omitting them can affect which couriers are eligible to accept the delivery"],"contributor":"waymark-seed","created":"2026-07-08T22:09:28Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/0a0df94f-e8a9-469d-8806-9773314a84bd"}