Authenticate to the Toast API using the client credentials OAuth 2.0 flow with your client_id and client_secret to obtain a Bearer token
Identify the menuItemGuid or modifierGuid for the item you need to 86 by querying the Toast Menus API for the target restaurant
Send a PUT or PATCH request to the stock endpoint with the item GUID and set the status field to indicate out-of-stock, following the current stock API request schema in the Toast developer docs
Parse the response to confirm the updated stock status was applied; handle 4xx errors such as 403 (missing scope) or 404 (item not found) explicitly
Optionally subscribe to inventory or menu webhooks to receive inbound 86 events when kitchen staff change availability from the POS terminal itself
When items become available again, send a subsequent request to clear the out-of-stock flag and restore normal ordering
Known gotchas
Stock status changes apply per-location; you must repeat the call for each restaurantGuid if the chain has multiple locations
The Toast stock API scope must be explicitly granted during partner onboarding; a missing scope returns 403 even with a valid token
Menu item GUIDs can change after menu republishes; always resolve GUIDs fresh from the Menus API rather than caching them indefinitely
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