Maintain a canonical hours-of-operation data store in your system with regular weekly hours and a list of holiday hour overrides keyed by date
For DoorDash Marketplace, use the store update endpoint in the Marketplace API to push hours as an array of day-of-week schedule objects; holiday overrides are submitted as special_hours entries with a specific date
For Uber Eats, use the Store Hours API under the eats.store scope to PUT the store's open/close schedule and submit override hours for specific dates
Schedule an automated job to push holiday overrides at least 72 hours before the date to ensure marketplace caches refresh before customers browse
Verify live hours by checking each platform's customer-facing app or store detail endpoint after each push
Known gotchas
Hours changes propagate to the customer-facing app with a delay of up to several hours on some platforms; do not assume immediate visibility after a successful API response
Submitting overlapping or contradictory holiday hours (e.g., a closure that overlaps a regular open window) can cause undefined behavior on some platforms — validate your payload for conflicts before submission
Some platforms distinguish between order-cutoff time and physical close time; set both correctly to prevent orders from being accepted after the kitchen has closed
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