Register for access to the NCR Voyix Business Services Platform developer sandbox through the NCR Voyix developer portal and obtain API credentials
Review the Restaurant APIs section of the NCR Voyix developer portal to identify the KDS routing and order management endpoints appropriate for your deployment type (Aloha Cloud vs. legacy Aloha POS)
Construct an order payload that includes the item and modifier details, the promised time for fulfillment, and any customer-facing notes you want displayed on the KDS
Submit the order via the appropriate NCR Voyix API endpoint; the platform will route the order items to the configured KDS stations based on the revenue center and item-routing rules set in Aloha
Poll or subscribe to order status change events through the API to track KDS bump status and calculate service time metrics
Test end-to-end in the sandbox environment, including KDS bump confirmation, before deploying to a production restaurant location
Known gotchas
Aloha Cloud and legacy on-premises Aloha POS have different API surfaces; confirm which deployment type your target restaurant uses before selecting endpoints
KDS routing rules (which items go to which display) are configured inside the Aloha back-office, not via the API; API calls must conform to the routing rules already set up in the POS
Promised time and customer note fields may not display on all KDS hardware models; verify display capability against the specific KDS hardware in use at each location
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