Set up integration with Loftware Cloud Trigger

The following procedure explains how to integrate Loftware Cloud Trigger (printing software) or Loftware Cloud Print with the Aptean Labeling extension:

1. Setup the Loftware Cloud Trigger.
   For more information, see Cloud Trigger – Loftware Help Center.

2. On the Labeling Setup page, in the Integration Type field, select Loftware Cloud Trigger.

   The Integration Type value field cannot be left blank. If it is blank, the system displays a notification on the Role Center indicating that it is not configured.

3. In the Endpoint Label Software field, enter the URL of the endpoint selected in the Integration Type field to send labels.You can use the default format https://labelcloudapi.onnicelabel.com/Trigger/v1/CloudTrigger/, where cloud trigger name varies based on the Loftware Cloud Trigger configuration.
4. In the Communication Type field, select the following communication type for label batching that allows optimization of API calls when printing multiple labels.
   • Single: Send labels individually in separate API calls.
   • Combined: Group multiple labels into a single API call.

• Ensure the relevant configurations are completed in the NiceLabel Cloud software for this functionality to take effect. To know more about the configurations on the NiceLabel Cloud software, see:
• Batch Printing
• Session Printing
• Configuring JSON filter.

7. On the Authentication FastTab, in the Authentication Type field, select Anonymous.

   

8. Enter the following header names and header values via Custom Http Headers. This is automatically added as additional http header values in the request to the NiceLabel Cloud as shown below:
   i. Api-Version, value as setup when creating the Cloud Trigger in Nicelabel Cloud, default is v1.
   ii. Ocp-Apim-Subscription-Key, key value from the Primary Key or Secondary Key field in the Loftware Developer Portal that is associated with the Lofware Cloud. For example: 12345e1fca123dc12a1e123456789b1e.

   

Based on the above setup, the headers are accepted in the NiceLabel Cloud environment: