Print Integration API Documentation
This documentation defines the data structures for sending print jobs to integrated destinations. These payloads are delivered either via a REST POST request or a Socket payload, depending on your specific integration tier.
Core Concepts
The printing model is hierarchical. A IPrintRequest represents a single print job (a "ticket"), which contains one or more IPrintRequestItem objects representing the specific items to be prepared or served.
Integration Method
Integrators may select with Socket or REST based integration. The Venue Administrator or NX Support Partner will configure the NX Printer Device within the NX Portal based on your selected integration method. A single integrator can select to use either method for integration.
Source of Data
NX's distributed nature means that requests may come from any NX POS Device. We suggest integrators not expect all traffic to come from a specific IP address, unless an integration-level limitation requires the same.
NX Orders, online & DSP orders, originate from the NX Cloud and are typically sent as server-to-server communication. NX strongly encourages Printing integrators to have Cloud based methods to receive orders. However, it is possible to route orders through the in-store POS Devices. Please contact NX Support if you need to support this functionality.