Use Uber Direct Robocourier for automated sandbox delivery testing

domain: developer.uber.com · 6 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

  1. Obtain Uber Direct sandbox credentials from the Uber Developer Dashboard.
  2. Create a delivery in the sandbox environment; include the test_specifications attribute in the CreateDelivery request body to trigger Robocourier instead of a real courier.
  3. Robocourier will automatically progress the delivery through status stages (courier_assigned, en_route_to_pickup, pickup_complete, en_route_to_dropoff, delivered) and fire corresponding webhook events.
  4. Configure your webhook endpoint to receive and process these sandbox events, validating your status-handling logic against each state transition.
  5. Do not create multiple Robocourier deliveries from the same pickup address in rapid succession; wait at least 90 seconds between deployments to avoid batching conflicts.
  6. Validate your webhook signature verification logic using the sandbox secret before moving to production.

Known gotchas

Related routes

Create a batched, multi-dropoff delivery with Uber Direct and correctly interpret dropoff_sequence_number and batch identifiers in status webhooks
developer.uber.com · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans