Query the Toast Configuration API for the modifierGroups resource for a given restaurant to retrieve all groups with their minSelections and maxSelections constraints
Identify groups where minSelections is greater than zero as required modifiers that must be enforced at order submission time
Export the modifier group structure including nested modifier-within-modifier relationships for items that support topping customization
Transform the Toast modifier schema into the target delivery platform's modifier format, preserving the min/max cardinality and nesting depth
POST the transformed modifier groups to the delivery platform's menu API and verify the required modifier UI elements surface in the consumer ordering flow
After any POS modifier group change, re-pull the Toast Configuration API and propagate the delta to all connected delivery channels within a defined sync window
Known gotchas
Toast modifier groups support multi-level nesting but most delivery platforms support only two levels; flatten deep nesting into composite modifier names before publishing
The Toast Configuration API returns modifiers in the POS display sort order, which may not match the desired consumer-facing order on delivery platforms; re-sort before publishing
Toast required modifiers (minSelections > 0) that have no default pre-selected option will block order injection from delivery platforms that do not surface the modifier prompt; always map a default value in the channel adapter
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