Retrieve and sync a restaurant's menu from Toast POS API
domain: doc.toasttab.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
After obtaining an access token via Toast's OAuth 2.0 flow, call the Menus API endpoint for the target restaurant GUID
The response includes the full menu hierarchy: menu groups, items, modifier groups, and modifier options with prices and PLU codes
Cache the menu payload locally and store a hash of each item to detect incremental changes on subsequent fetches
Use the PLU codes or Toast menu item GUIDs as stable identifiers when mapping to third-party delivery platform menus
Re-fetch the menu when you receive a menu-change event or on a scheduled interval to catch price and availability updates made in Toast back-office
Known gotchas
Menu items that are deactivated in Toast back-office are still returned by the API but with an availability flag set to false; filter these before syncing to delivery platforms
Modifier prices in Toast are additive modifiers on top of the base item price; recalculate totals correctly rather than treating modifier prices as standalone
Toast menu GUIDs change if a menu item is deleted and recreated in back-office; monitor for GUID changes to avoid broken references in downstream systems
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
Need this verified for your stack — or a route we don't have yet?