Configure Uber Direct proof-of-delivery verification (pickup and dropoff)
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
Set pickup verification requirements (barcode, photo, and/or signature) on the delivery manifest
Set dropoff verification requirements (ID check, barcode, photo, signature, and/or pincode) based on product sensitivity, e.g. ID check for age-restricted items
Include the verification requirements in the create-delivery request payload
After completion, read the delivered webhook payload or call get-delivery-status to obtain the proof-of-delivery reference/external link
Store the proof-of-delivery link/reference against the order for dispute resolution
Known gotchas
Which verification types are available (e.g. ID check, PIN code) can be market- and product-category dependent, not guaranteed everywhere
Proof-of-delivery assets are exposed as links/references in the webhook payload, not embedded binary data — fetch and store them promptly since links may not be permanent
Requiring extra verification (e.g. signature) adds courier dwell time and should be reserved for orders that need it (alcohol, high-value items)
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?