Print Job Status
Last Updated: July 10, 2026
The Print Job Status API returns a request to the customer application with the status of the print job associated with the Universally Unique Identifier (UUID). The Print Job Status API has two options that differ in the communication route. When using Print Job Status, the API Print Service initiates the request to the customer application after a printing event. The Print Job Status Callback schema responds with the status only when the customer application requests it. Use the schema below to configure this API call for the API Print Service.
Key Points
- The customer application initiates the request to the API gateway which responds back with the status.
Troubleshooting Help
In some setups, external applications may need to reach the Virtual Appliance Output Service Agent using a DNS name that resolves to an external IP address. However, this can cause issues the following issues:
- The Service Agent cannot resolve the DNS name to its internal IP address.
- External DNS resolution conflicts with internal requirements.
Check if the Service Agent can resolve the DNS name to its internal IP address. If the DNS name doesn't resolve correctly, you may need to modify the hosts file. See Troubleshoot DNS Resolution for Output Automation Service Client
Ensure that the DNS name in the UI matches the one in the certificate used by the Service Agent.
In this topic:
PrinterLogic Output modernizes traditional output management by automating critical document and print workflows, bridging back-end systems and end-user printing, and connecting seamlessly with existing EMR, EHR, and ERP systems. PrinterLogic Output automates document routing, conversion, and delivery, reducing manual effort and streamlining operations
- EMR/EHR/ERP Connectors
- API Service
- Output Rules
- Batch Printing
PrinterLogic Outputis licensed per print queue. You will need additional licensing to access additional features like Secure Release and Off-Network Printing.
As a PrinterLogic Output customer, you will already have a functional Service Agent and printer configured. From there, you must secure a digital certificate issued by a reputable Certificate Authority (CA), recognized and trusted by the system or application you are connecting to the Output Service.
For additional information on API Print Serviceprerequisites, refer to .
The API Print Service runs on the PrinterLogic Output Service on a Windows or Debian Linux server either on-premise or in your cloud instance. This allows the API Print Service to reach your source application and printers unless Off-Network Print is utilized. This back-end configuration is flexible to your environment’s requirements to function seamlessly with your existing systems and processes.