Subscribe to Toast order fulfillment status webhooks for kitchen display routing
domain: doc.toasttab.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register your integration in the Toast Developer Portal and obtain OAuth credentials for the target restaurant location.
Configure a subscription to the guest_order_fulfillment_status webhook, which fires when an order moves between kitchen fulfillment stages.
Implement the webhook receiver endpoint to accept POST requests from Toast, verifying the request origin using Toast's signing mechanism.
Parse the fulfillment status payload to extract the order ID, new fulfillment stage, and timestamp; map these to your kitchen display system's internal state machine.
Acknowledge receipt with HTTP 200; Toast will retry delivery for non-2xx responses.
Subscribe additionally to the restaurant_availability webhook if your system needs to detect when the restaurant suspends online ordering (e.g., during rush periods or technical issues).
Known gotchas
Toast's webhook events are restaurant-location scoped; a multi-location integration must subscribe independently per location GUID — there is no single global subscription for an enterprise brand.
The Orders API by default creates orders for immediate fulfillment without verifying restaurant service hours; your integration must independently check restaurant availability before injecting an order.
Toast's developer portal access and API credentials require enrollment in the Toast Partner Program for production use; sandbox credentials are available separately for development.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?