Waymark / Routes / doordash.com Create white-label deliveries with DoorDash Drive
domain: doordash.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Generate a signed JWT using your DoorDash developer_id, key_id, and signing_secret; set alg to HS256 and include an exp claim 5 minutes in the future POST to https://openapi.doordash.com/drive/v2/deliveries with the JWT in the Authorization: Bearer header Include pickup and dropoff addresses, contact names, phone numbers, and order_value in cents in the JSON body Optionally request a quote first via POST /drive/v2/quotes, then accept it via POST /drive/v2/quotes/{quote_id}/accept before creating the delivery Store the returned external_delivery_id for subsequent status polling or webhook correlation Poll GET /drive/v2/deliveries/{external_delivery_id} or rely on webhooks to track lifecycle events Known gotchas JWTs must be freshly generated per request; a reused or expired token causes 401 errors — do not cache them The Drive v2 API requires partner onboarding and sandbox approval before production access; contact DoorDash developer support to get credentials order_value is required and must be in cents; omitting it or passing zero can cause dasher dispatch failures
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