We've Moved!
We've unified our Vasion Print (formerly PrinterLogic) and Vasion Automate documentation into a single, streamlined resource to better serve you. Visit our new unified documentation site: docs.vasion.com
Note: This legacy site will not be updated after January 6, 2025, and will remain available for reference until May, after which all traffic will automatically redirect to docs.vasion.com/a/Get_Started/Automate.htm.
Last updated: January 07, 2025
Configure API Print Service
The Vasion Print (formerly PrinterLogic) API Print Service provides printing capability from systems that don't typically support it by accepting print jobs via web requests. You can eliminate the need to install print queues on your source application and move to a driverless print model, reducing the work required to maintain the print environment.
Requirements
-
You must have a functional Service Client that meets the minimum required specifications. See Service Client.
Running IPv6 on your Windows Service Client may cause conflicts. You may need to disable IPv6 on the Service Client's network adapter to resolve the conflict.
-
Your Service Client must be able to access
https://agent-api.app.printercloud.com/
.- If you are also using Off-Network Print, your service client must be able to access the following:
ofn.app.printercloud.com
ofn-gw.app.printercloud.com
Ensure you add the region code after printercloud, if applicable. Example: For Canada, add a 15 after printercloud:https://agent-api.app.printercloud15.com/
, EMEA add a 5, APAC add a 10, Singapore add a 20. - If you are also using Off-Network Print, your service client must be able to access the following:
- Have a certificate signed by a Certificate of Authority (CA) trusted by your source application.
Enable API Print Service
- In the Admin Console, select the Service Client where you want to configure the API Print Service.
- Select the Output Automation tab.
-
Enter the DNS Name of the Service Client you are using for Output Automation.
This DNS name must match the device certificate name if using IPPS. The Service Client must map this DNS name to its local IP address. If this field is empty, the service will fail to start, and a "Failed to get host address" error is added to the log.
-
Scroll down to the API & IPP Print Service section and select Enable API Print Service.
-
If your application is secured, you can select Enable Basic Authentication to generate an authorization code or enter a code from your application to provide authorization to send jobs to Vasion Print (formerly PrinterLogic).
- If you have a code from your application, highlight and delete the generated code and enter your application's code.
- Select Save.
Certificate
You only need to employ a certificate trusted by the source application if you use IPPS. Follow the steps below:
-
Select Enable TLS on IPP(S) Service.
-
Enter the information for your certificate using one of the following options:
The Status section displays a green circle and states the service is Online when everything is configured correctly.
Supported API Calls
Once configured, your source application can make RESTful API calls. Below is a brief overview. For complete schemas, see API Print Service Schemas
Print Job Request
Sends the file to be printed to the API Print Service along with metadata about the file that dictates where the job is sent, as well as color, duplex, and other finishing options.
Batch Open Request
Ensures certain files are printed in a specific order. Batch Open Request is used to begin the batch printing process and includes an ordered list of print job UUIDs and files.
Batch Close Request
Sent after a Batch Open Request and all associated files have been sent. Once a batch is closed, the files with UUIDs listed in the initial Batch Open Request are printed in the order the UUIDs were listed in the initial request.
Print Job Status
Once a job has been printed, or if it failed to print, the API Print Service will make a request back to the URL specified in the "statusURL" field as part of the initial print job request to inform the customer application on the status of the print job with the associated UUID.
Optional Next Step
Troubleshooting Help
In some setups, external applications may need to reach the Output Automation Service 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.
-
Week Ending In Jan 4th, 2025
-
Released: Dec 27th, 2024
-
Released: Dec 23rd, 2024
-
Android/iOS: Dec 23rd, 2024
-
Released: Dec 9th, 2024