Verify Uber Direct webhook signatures and handle exponential-backoff retries
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
Register an HTTPS webhook endpoint for delivery status notifications in the Uber Direct customer settings
On each incoming POST, compute a SHA-256 HMAC over the payload using your signing key and compare it to the x-uber-signature header before processing
Return a 200 response with an empty body promptly to acknowledge receipt
If your endpoint fails to acknowledge, expect Uber to retry with exponential backoff starting at 30 seconds, then 60s, 120s, and so on, up to 7 attempts
Design the handler to be idempotent (dedupe on delivery id + event type) since retries can deliver the same event more than once
Known gotchas
If no 200 is ever received after 7 attempts, the event is dropped — poll get-delivery-status as a fallback rather than relying solely on webhooks
The signature header (x-uber-signature, SHA-256) and retry cadence are Uber-specific and differ from DoorDash's Basic Auth/OAuth webhook model
Webhook retries are not guaranteed to arrive in order — check the event/delivery status field rather than assuming the last-received event is most current
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?