Print Job Status
Last Updated: March 17, 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). Use the schema below to configure this API call for the API Cloud Link.
The API Server and Authentication sections below are for the API Cloud Link feature. Customers configuring API Cloud Link will use the endpoint and token outlined on Configure API Cloud Link.
Key Points
- This schema supports API Cloud Link. For API Print Service schemas, go to API Print Service Schemas.
- Use the API Server below adjusted for your region.
- The customer application initiates the request to the API Cloud Link gateway which responds with the status.
Troubleshooting Help
In some setups, external applications may need to reach the Vasion OutputService Client using a DNS name that resolves to an external IP address. However, this can cause issues the following issues:
- The Service Client cannot resolve the DNS name to its internal IP address.
- External DNS resolution conflicts with internal requirements.
Check if the Service Client 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 Client.
Vasion 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. Vasion Output automates document routing, conversion, and delivery, reducing manual effort and streamlining operations
- EMR/EHR/ERP Connectors
- API Service
- Rules & Routing
- Batch Printing
- Output Console
- Print Job Regionalization
- Document Conversions & Driverless Printing
- Confirmed Delivery
- Quick Configuration
- API Cloud Link
Check out our Vasion Output Solution Brief. for more about these features.
Yes, Vasion Output easily connects your systems with Vasion to route and deliver documents to your desired destinations while offering you more granular control and visibility.
It seamlessly connects with ERP/EMR/CRM systems and other business-critical applications, enhancing your current document management without needing a complete overhaul. The API Service also supports on-prem and cloud-based systems, expanding your integration capabilities with ease and flexibility.
The Output Console offers complete control and oversight over your printing and document environment. This unified interface offers the ability to view printers, filter and sort print jobs, track processed jobs, redirect failed print jobs, and cancel or reprint past jobs. With robust reporting capabilities, you gain enhanced insights into queue statuses and printer performance, ensuring efficient, transparent print operations. Reduce downtime by quickly identifying and troubleshooting issues to protect your critical business processes.
Vasion Output is easy to implement. Tools like Network Scanner, the Data Manager, and Quick Config tool help you migrate queues and apply settings in bulk. You can also configure zones to route jobs by region and use the Output Console for real-time monitoring, job health, and automatic redirection.
Vasion Output is licensed per print queue. You’ll need additional licensing to access additional features like Secure Release and Off-Network Printing.
As a Vasion Output customer, you will already have a functional Service Client 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 the API Print Service prerequisites, visit our API Print Service Connector documentation.
The API Print Service runs on the Vasion 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.