Use the DoorDash Marketplace Item 86'ing webhook endpoint to send a real-time availability update without resubmitting the full menu
Build the request payload with a list of item identifiers and a set_inactive boolean; to restore an item, send the same list with set_inactive set to false
Keep each request to a maximum of 40 items or item options; split larger batches across multiple sequential calls
Rate-limit your caller to stay within 480 requests per minute for the item availability endpoints to avoid throttling
Confirm the change by fetching the item status via GET store and menu info endpoint and verifying the item's active field
Known gotchas
Exceeding the 40-item-per-request limit causes the entire batch to be rejected, not just the overflow items — always paginate large 86 operations
After a full menu re-push, 86'd items may be reset to active; re-apply out-of-stock flags after any full menu synchronization
The 86'ing endpoint operates on item option (modifier) IDs as well as item IDs; ensure your lookup table includes modifier-level identifiers if modifier-level 86'ing is needed
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