Input Commands
Data controllers are also referred to as inputs and/or profiles. called an input. These commands allow you to creating, modify, and attach profiles and data controllers.
Assign an input to the title.
optional id to track this command, will be returned in the response
optional: UUID of title/layer to operate on
optional: Name (or UUID) of the title to operate on.
Testoptional: Input name, used to select the title(s) to operate on
inputNamewhen 1, the new input will be combined with existing inputs on the title
successful operation
bad request
Connects a specific input profile to a title. It works exactly like setTitleInput except this command allows you to use 'input' to find a title by input while that one reuires the use of title name/id.
Because this endpoint doesn't use any variables, it can also be accessed using a GET request.
optional id to track this command, will be returned in the response
optional: UUID of title/layer to operate on
{218f46f9-e881-49a8-ab17-03c8f9cc8461}optional: Name (or UUID) of the title to operate on.
optional: Input name, used to select the title(s) to operate on
set to 1 to merge the new input with existing inputs
Name of profile (data controller) to add to the found title(s)
Test: Profile Namesuccessful operation
bad request
Renames an input controller.
optional id to track this command, will be returned in the response
Name of input / profile to change.
Test: Input Name 1New name to assign to it.
Test: Dog Walker Mark 5successful operation
bad request
Creates an input dynamically at runtime. The profile field must contain the full XML of an input. After creating an input, you can then assign it to a title by name using the attachProfile command. NOTE: This function can only be used through the scheduleCommandXml API as shown below:
Because this endpoint doesn't use any variables, it can also be accessed using a GET request.
successful operation
bad request
NOTE:
setProfilerequires submitting xml data, so to use it, unless your xml data is small, you might need to send it as a POST request to the/api/endpoint directly.
Last updated