Query restaurant configuration and location details from the Toast Restaurant 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
Authenticate using OAuth 2.0 client credentials with management_groups or restaurant_info read scope
Call the restaurant info endpoint with the restaurant GUID to retrieve general configuration (name, address, timezone, currency)
Retrieve the restaurant's service area and table configuration if your integration supports dine-in or delivery zone features
Use the management group endpoint to list all restaurants under a multi-location enterprise account
Cache restaurant metadata and refresh periodically; include the restaurant GUID in all subsequent Toast API calls for that location
Known gotchas
Restaurant GUIDs are the stable identifier in Toast; external IDs are optional — always store the Toast GUID as your primary key for a restaurant
Some configuration fields are only visible to integrations with elevated partner scopes; request appropriate scopes during the partner onboarding process
Management group access allows listing restaurants, but each restaurant still requires a separate authenticated request scoped to that restaurant GUID
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