Register your application in the Toast Developer Portal to receive a client ID and client secret
Implement the OAuth 2.0 client credentials flow to obtain an access token from Toast's token endpoint using your client credentials
Include the required Toast-Restaurant-External-ID header on all restaurant-scoped API calls to target a specific restaurant
Use the Toast sandbox environment for initial integration testing; request access to a sandbox restaurant GUID from Toast
Submit your integration for Toast's partner review process before going live with production restaurant credentials
Known gotchas
Toast uses a restaurant-scoped authentication model; a single access token is not sufficient — you must target the correct restaurant via headers or restaurant-specific credentials
Toast's partner API is not open to all developers; production access requires approval through Toast's partner program
Sandbox and production environments use separate base URLs and credentials; do not mix them
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