See the chapter API Methods for a list of fields applicable to your particular API method. Fields you use depend on your API method. The data structures below include all possible fields. You can have multiple on-premise NiceLabel Automation servers running the same configuration at the same time with automatic round-robin load balancing enabled. When you execute Cloud trigger APIs, your NiceLabel Cloud account knows where your registered Automation trigger is running and forwards data to your trigger. You can access the triggers with Cloud trigger APIs. When you load and deploy/activate your Automation configuration, Automation registers the Cloud triggers (unique names) in your NiceLabel Cloud account. Unique names tell Automation which trigger it must execute. One trigger for the PRINT method, another for the PREVIEW method, and yet another for the PRINTERS method, etc. You use different triggers for each method. In the example below, replace the “unique_name_of_the_Cloud_trigger” with the actual unique Cloud trigger name defined in your NiceLabel Automation configuration (.MISX file).Įach Cloud trigger defined in your configuration exposes one API method. You must reference the unique name in each HTTP request to our Cloud trigger API. Each Cloud trigger is identified by a unique name.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |