Authenticate with a DoorDash Developer OAuth client credentials token scoped to the store-management API
Send a PATCH to the store availability endpoint with is_paused set to true and a pause_reason_code (e.g. KITCHEN_CAPACITY) to stop new orders from flowing
Set a resume_time timestamp so the platform auto-unpauses at a defined future moment without a follow-up API call
Poll the store status endpoint or listen to a STORE_PAUSED webhook to confirm the state change propagated
When capacity recovers, send a PATCH with is_paused set to false or allow the auto-resume timer to fire
Log pause durations and correlate with order volume data from financial reports to tune capacity thresholds
Known gotchas
Auto-resume via resume_time may lag by a few minutes in practice; do not rely on it for sub-minute precision in high-demand environments
Repeated store pauses within a short window can trigger a partner review by DoorDash operations; space pause/unpause cycles appropriately
Pausing a store does not cancel in-flight orders already accepted; those must be managed separately through the order cancellation flow
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