Authenticate using Toast's partner API credentials; obtain a short-lived access token from the Toast authentication endpoint using your client_id and client_secret
Fetch menu data by calling GET /menus/v3/restaurants/{restaurantGuid}/menus — this returns the full menu hierarchy including categories, menu groups, items, modifier groups, and modifier options in a single response
For order export, call GET /orders/v2/orders with the required restaurantGuid header and optional filter parameters such as startDate, endDate, and pageToken for pagination
Parse the Order objects to extract line items, modifiers, payment details, and tips; use the displayNumber field for human-readable order references
Use webhooks (available via Toast's webhook configuration) to receive real-time order events rather than polling for high-volume integrations
Store the guid values for menu entities to map order line items back to menu items during reconciliation
Known gotchas
The menus v3 API is the current version; v1 and v2 are legacy and should be avoided for new integrations
Toast's API access is partner-gated and requires an approved integration listing in the Toast Partner Ecosystem; self-serve access is not available for production restaurants
Pricing data in the menus API may not reflect all modifiers and combo pricing; for pricing verification, use the POST /orders/v2/prices endpoint
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