Register your application in the DoorDash Developer Portal and obtain a developer ID and signing secret for the target environment (sandbox or production)
Generate a short-lived JWT for each API request by signing a payload containing your developer ID, key ID, and issued-at/expiry timestamps using your signing secret
Request a delivery quote by POSTing order details (pickup address, dropoff address, item count, and optional declared value) to the quote endpoint; validate that the quote covers your desired delivery window and price
Accept the quote by creating a delivery, supplying the quote ID alongside pickup contact and dropoff contact details, and any special handling instructions relevant to grocery (e.g., leave at door, no contact delivery)
Store the returned delivery ID; poll the delivery status endpoint or receive status updates via webhook to track shopper assignment, pickup, and dropoff
Handle the return-to-store flow by configuring the undeliverable action in your create-delivery payload so that items are returned to the dark store if the customer is unreachable
Known gotchas
Production access to the DoorDash Drive API is restricted and requires completing development in sandbox and submitting a production access request — DoorDash cannot guarantee a certification timeline; plan onboarding lead time accordingly
JWTs are short-lived and must be generated per-request; reusing a token after its expiry will result in authentication errors — build JWT generation into your request middleware
Declared item value affects delivery cost and insurance thresholds; inaccurate declared values for high-value grocery orders may affect claim eligibility if items are lost or damaged
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp