Set up a kiosk ordering integration with Toast by configuring the integration through the Toast Developer Portal and injecting orders from a self-service kiosk into Toast POS
Apply for integration partner status through the Toast Developer Portal and request access to the kiosk or ordering integration API scope during the partner vetting process
Obtain a client_id and client_secret from the Toast developer dashboard and implement the client credentials OAuth 2.0 flow to generate Bearer tokens for API calls
Build the kiosk ordering UI using your own interface and menu data sourced from the Toast Menus API, ensuring modifier groups and prices stay in sync with the restaurant's current Toast configuration
When a customer completes a kiosk order, construct a Toast order payload and POST it to the Toast Orders API endpoint for the target restaurant GUID, including line items, modifiers, fulfillment type, and any loyalty or promo identifiers
Handle the response to retrieve the Toast-generated check GUID and surface the order number or confirmation to the guest on the kiosk screen
Test the full order flow end-to-end in the Toast sandbox environment, including modifier pricing and kitchen ticket routing, before going live
Known gotchas
Toast requires Restaurant Management Essentials or Pro suite for partner integrations and API access; confirm the restaurant account tier before beginning integration work
Kiosk orders must include the correct service area or dining option identifier; misconfigured dining options can cause the order to route incorrectly in the kitchen or fail validation
Menu data from the Toast Menus API should be refreshed after any menu publish event; stale menu data on the kiosk can lead to orders being rejected if items or modifiers have changed
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