API Print Service Schemas

You'll need to configure settings for the API Print Service in two places:

  1. In the Vasion Print (formerly PrinterLogic) Admin Console.
  2. Inside your source application to make RESTful API calls for submitting print jobs or batch print requests.

For complete information about Output Automation, see Output Automation.

For information on how to configure the API Print Service, see Configure API Print Service.

Supported API Calls

Once configured, your source application can make the following RESTful API calls:

  • 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 to an API Print Service. Once a batch is closed, the files with UUIDs listed in the initial Batch open request will be 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.

API Schemas

Below is the recommended schema for configuring your API Print Service. There are two schemas, one for Print Job Requests and one for Print Job Status Reply. Within the Print Job Request schema there are also options for Batch Printing.

Print Job Request

Print Job Status

Troubleshooting Help