OnTheAir Video REST API

OnTheAir Video's REST API allows you to retrieve OTAV's status, change playlists, do controls of the playback and playing with the DGO. Also note that this REST API is not final, it's a first draft and there could be changes in the future when it is finalised.

This API is meant to be RESTful, then, using different verbs on requests leads to different behaviour on request processing.
In general manner, consider theses verbs to have the described behaviour:

When you modify or retrieving data, be sure to handle properly the return code that is returned by the API as it indicates if the operation was successfull or not.
For POST & PUT requests you MUST supply the 'Content-Type' header with value 'application/json'.
Here is a short list common codes returned by the API:

Code Meaning Description
200 OK The request was succesfully processed.
201 Created A new resource has been created on server side.
202 Accepted The resquest was accepted but was not processed.
400 Bad Request The resquest was not well formed.
401 Unauthorized The request needs an access token to proceed. See Authorization
403 Forbidden The token provided doesn't have sufficient privileges/permissions. See Authorization
404Not found The resquest couldn't be processed. The path is not recognized.
422 Unprocessable entity The resquest is well formed but is sementically incorrect

To know if your request succeded; command, update, create and delete requests are followed with this kind of response:

Command response object:

{
	"success" : boolean,
	"error" : string OPTIONAL
}

"success": Indicates if the request was accepted and processed or not by OnTheAir Video.
"error": In case of success false, indicates what was wrong when processing the request.


NOTE:
OPTIONAL marked parameters indicates that these parameters can be or not be present in the response object, this is due to internal logics.
However for requests that require a body, like PUT or POST, it means that it can be passed but they are not mandatory.



Authorization

Since playlists can play sensitive content at a time, an authorization mechanism will be required if you decide to enable it in OnTheAir Video's preferences. (General -> HTTP Server -> Require Authentication).

If this feature is enabled, it implies that you have to login with one of the registred user defined in OnTheAir Video and use the token received. In case not, you can ignore this section.

Each user has an access level, it defines how much control you have.
Theses are described as follows:

# Title Description
1 Read Only You'll only be able to retrieve informations but not modifying it.
2 Modify Playlists You'll only be able to modify playlists.
3 Modify And Control Playlists You'll be able to modify playlist, control the playback and DGO.
4 Full Access You'll be granted to execute all commands (admin privileges).

In order to make request you must first login with the following request:

PUT /authorize
{
	"username": string, REQUIRED
	"password": string REQUIRED
}

Response:
{
	"token": string, OPTIONAL
	"error": string, OPTIONAL
	"level": number
}

The token received MUST be added in the query parameter of each request you make to OTAV.
The level property is indicating the level granted to the logged user as defined in the table above.

NOTE:



Unique id - index or display name ?

Each playlist can be addressed using either its unique_id or its index.

Each clip can be addressed using either its unique_id, its index or eventually its display name.

Each action can only be addressed by its unique_id.



Getting informations about the OnTheAir Video Instance

GET /info
Response: Infos object

Infos response object:

{
	"available_actions" : array <string>,
	"time_zone" : string, eg: "America\/Los_Angeles"
	"name" : string,
	"application_version" : string,  eg: "4.1.1b2"
	"is_player_capable" : boolean
}


Get available transitions

GET /playback/transitions
Response: array <string>



Getting the Playback status

Get the "generic" playback status of OnTheAir Video

GET /playback/playing
Response: playback status object

Playback response object:

{
	"current_date_time" : string eg: "2023-03-08 12:53:03"
	"is_playing" : boolean,
	"is_paused" : boolean,
	"is_locked" : boolean,
	"item_index" : number, OPTIONAL * eg. 3
	"item_display_name" : string, OPTIONAL * eg. "My Movie Name"
	"item_duration" : number, OPTIONAL * eg. 233.3199
	"item_elapsed" : number, OPTIONAL * eg. 152.5200
	"item_filename" : string, OPTIONAL * eg. "MyMovie1"
	"item_media_url" : string, OPTIONAL * eg."file:\/\/\/Volumes\/Videos\/MyMovie1.mov",
	"item_remaining" : number, OPTIONAL * eg. 65.03
	"item_path" : string, OPTIONAL * eg. "/Volumes/Videos/MyMovie1.mov"
	"item_playback_status" : string, OPTIONAL * 
playback mode
"item_unique_id" : string, OPTIONAL * eg. "666AD1EF-54C6-4A63-A67B-501C57E6080F" or "" if not playing "live_subtitling" : boolean, OPTIONAL * "next_live_display_name" : string, OPTIONAL * eg. "My Live Name" "next_live_unique_id" : string, OPTIONAL * eg. "666AD1EF-54C6-4A63-A67B-501C57E6080F" or "" if no live in currently playing playlist "playback_status" : string, OPTIONAL * eg. "Playing", "Stopped", "Pause" "playlist_display_name": string, OPTIONAL * Playing playlist's name "playlist_duration" : number, OPTIONAL * eg. 233.3199 "playlist_elapsed" : number, OPTIONAL * eg. 233.3199 "playlist_index": number, OPTIONAL * Playing playlist's index (in opening order) "playlist_remaining" : number, OPTIONAL * eg. 80.7999 "playlist_unique_id": string, OPTIONAL * Playing playlist's unique ID "remaining_time_until_next_live" : number, OPTIONAL * eg. 233.3199 }

*: Thoses fields will only appear if a playlist is playing


Get the playback status of a playlist

With the following request, you will get a few info about the status of the playlist, and more. See playlist section for more controls.
GET /playlists/{n}/playing
Response: command response object


Get the playback status of a clip

With the following request, you will get a few info about the status of the clip, and more. See clips section for more controls.
GET /playlists/{n}/items/{m}/playing
Response: command response object



Getting thumbnails of video output

Retrieve the thumbnails of the video output. Allows to have a small preview remotely.


Get available transitions

GET /playback/thumbnail
Response: jpeg data



Playback Controls

Types of controls

You have three ways to control the playback. Depending on what you want to achieve, you can:

  • address "playback" and NOT specify a playlist, nor a clip. In this case, the playing playlist (or the front one if no playlist is playing) will be the one answering your requests.
  • specify the playlist you want to control (by using its index or unique ID), but without specifying a clip. In this case you can start the playback on a specific playlist, and the first clip (or the playing one) in the playlist will be controlled
  • specify both the playlist you want to control, as well as the clip (by using their index or unique ID). That's the way to start playing a specific clip in a specific playlist.

NOTE:
When using playback commands (play or pause) by specifying a clip, the following parameters can be passed in the URL to set the playback's play head at a precise timecode:

 "position_relative_timecode": string HH:MM:SS:FF timecode position from the clip's start
 "position_media_timecode": string HH:MM:SS:FF absolute timecode in the media
 "position_relative_seconds": number position after x seconds from the media's beginning
 

Below, you will find the 3 types of controls (generic, per playlist or per clip). Depending on the type of command, you may have just one control possible. Or in some cases, all three are possible but will produce the same result. For example, if you aska a "generic" stop, it will do a stop the same way as if you specify a clip and/or a playlist.


The basic - play/stop/pause

Play

Start playing at the beginning of the front playlist:
GET /playback/play
Start playing at the beginning of the specified playlist:
GET /playlists/{n}/play
Start playing at the the specified clip of the specified playlist (see above to also specify an offset to start the clip):
GET /playlists/{n}/items/{m}/play
Response: command response object


Stop

All three requests will stop the playback, whatever playlist is playing.
GET /playback/stop
GET /playlists/{n}/stop
GET /playlists/{n}/items/{m}/stop
Response: command response object


Pause

If a playlist is playing or paused, the first 2 requests will control the "playing or paused" playlist: pause the playback if playing or resume it if paused. If nothing is playing, the first request will do a pause on the front playlist, on the selected clip if any. The second request will specify on which playlist the pause should be done.
GET /playback/pause
GET /playlists/{n}/pause
Even if something is playing or paused, the following request will ask to pause the clip. Never to resume it.
GET /playlists/{n}/items/{m}/pause
Response: command response object


Resume

As the pause control can either do a pause or resume, if you want to be sure to do a resume, you should use this one, instead of the pause... Whatever three requests, it will do a resume of the paused clip if any, in whatever playlist.
GET /playback/resume
GET /playlists/{n}/resume
GET /playlists/{n}/items/{m}/resume
Response: command response object


Skip to previous/next

Skip to next

All three commands will do a skip to next on the playing playlist... Nothing will happen if nothing is played or paused.
GET /playback/skip_next
GET /playlists/{n}/skip_next
GET /playlists/{n}/items/{m}/skip_next
You can also indicate if the skip to next should only be done if the currently playing item is a live (useful to exit a live, but ignore if you are already out of the live).
GET /playback/skip_next?live_only=1
Response:

{
	"success": boolean,
	"last_position": number Indicates the elapsed time of the previously playing clip in seconds.
}


Skip to previous

All three commands will do a skip to previous on the playing playlist... Nothing will happen if nothing is played or paused.
GET /playback/skip_previous
GET /playlists/{n}/skip_previous
GET /playlists/{n}/items/{m}/skip_previous
Response: command response object


Play next

Play next (clip)

Set which clip will play once the current one is done playing (or when doing a skip to next). This request only works when specifying a playlist and a clip.
GET /playlists/{n}/items/{i}/play_next
Response: command response object


Clear next (clip)

All three requests will clear the clip that was previously set as the next to play.
GET /playback/clear_next
GET /playlists/{n}/clear_next
GET /playlists/{n}/items/{m}/clear_next
Response: command response object


Other controls

Cue trigger

Emulates the "space bar". If you want to do as if you were using the space bar on your computer...
GET /playback/cue_trigger
Response: command response object


GPI trigger

Emulates a "GPI input" received trigger. You must specify the input number. This will do a skip to next if a "GPI trigger" for the specified input is set on the currently playing clip (cf clip attributes inspector)
GET /playback/gpi_trigger?input=1
Response: command response object


Join in progress

This feature is only available if you have the traffic option, will use the theoretical start date/time of the playlist and clip in order to start playing what was scheduled to play. The first request will do a join in progress, in the following order, on: the playing playlist; if no playlist is playing, the playlist of the day; if no playlist is playing, nor a playlist of the day is open, the front playlist
GET /playback/join_in_progress
The following two requests will do a join in progress on the specified playlist.
GET /playlists/{n}/join_in_progress
GET /playlists/{n}/items/{m}/join_in_progress
Response: command response object



Working with Subtitles

Get playback's subtitles

GET /playback/subtitles
Response: array <subtitle record object>

Subtitle record response object:

{
	"start_time_seconds": number,
	"start_timecode": string,
	"end_time_seconds": number,
	"end_timecode": string,
	"text_lines": array <subtitle line>
}

Subtitle line response object:

{
	"alignment": string, eg. "center" see 
alignment type
"text": string }

Adding subtitles to current playback

POST /playback/subtitles

Subtitle record object:

{
	"start_time_seconds": number, REQUIRED
	"start_timecode": string, OPTIONAL Format HH:MM:SS,ttt
	"end_time_seconds": number, REQUIRED
	"end_timecode": string, OPTIONAL Format HH:MM:SS,ttt
	"text_lines": array <subtitle line> REQUIRED
}

Subtitle line object:

{
	"color": string, eg. "#ff00ff" OPTIONAL
	"alignment": string, 
alignment type
OPTIONAL "vertical_position": number, eg. 11 OPTIONAL "text": string }
Response: command response object

NOTE:
"end_time_seconds" property override the "end_timecode" property.
"start_time_seconds" property override the "start_timecode" property.




Control the DGO

Get the DGO projects:

Here are examples of requests to get the available CG projects or a specific project designated by {n}:

GET /playback/cg_projects
Response: array <CG Project object>
GET /playback/cg_projects/{n}
Response: CG Project object

CG Project object:

{
	"unique_id" : string,
	"formatted_elapsed_time" : string, eg. "00:00:00"
	"formatted_duration_time" : string,
	"formatted_remaining_time" : string,
	"published" : boolean,
	"display_name" : string, eg. "AnalogClock"
	"display_mode" : string, OPTIONAL eg. "1080i 59.94"
	"width" : number, OPTIONAL eg. 1920
	"height" : number, OPTIONAL eg. 1080
	"frames_per_second" : number, OPTIONAL
	"metadata" : object,
	"path" : string, eg. "\/Applications\/OnTheAir CG\/Projects\/AnalogClock.cg3"
	"remaining" : number,
	"elapsed" : number,
	"duration" : number,
	"status" : string  eg. "Loading"
}


Play/Pause/Stop a DGO project:

Play

PUT /playback/cg_projects/{n}/play
Response: command response object

Pause

PUT /playback/cg_projects/{n}/pause
Response: command response object

Stop

PUT /playback/cg_projects/{n}/stop
Response: command response object

Additional commands:

Getting the thumbnail of a project

PUT /playback/cg_projects/{n}/thumbnail
Query parameters:
	"width"  REQUIRED
	"height" REQUIRED
Response: image/jpeg DATA or command response object

Close the project

PUT /playback/cg_projects/{n}/close
Response: command response object

Scrub in the project

PUT /playback/cg_projects/{n}/scrub
Query parameters:
	"position" REQUIRED
Response: command response object


Get the CG items of a DGO project:

GET /playback/cg_projects/{n}/items
Response: array <CG Item object>
GET /playback/cg_projects/{n}/items/{i}
Response: CG Item object

CG Item object:

{
	"unique_id" : string,
	"type" : string,
	"display_name" : string,
	"frame" : number,
	"begin_time" : number,
	"hold_duration" : number,
	"stay_forever" : boolean,
	"is_locked" : boolean,
	"is_hidden" : boolean,
	"is_published" : boolean,
	"default_value" : string
}


Modify the items of a DGO project:

Below are example of request that you can use to modify the items {i} of a DGO project {n}:

Modifying text items

PUT /playback/cg_projects/{n}/items/{i}
Body:
{
	"text" : string, OPTIONAL eg. "This is my new text"
}

Modifying rich text items

PUT /playback/cg_projects/{n}/items/{i}
Body:
{
	"htmlText": "<span style='font-family:Courier; color:red; font-size: 20;'> 20px red text. </span>
<span style='font-family:Courier; color:blue; font-size: 50;'> 50px blue text.</span>"
}

Change Movies items

You can change the path of a movie item using either the full path or the relative path. When using the relative path, this means that the file used will be found relatively to the location of the project itself. This allows you then to move the project and media to another location, and this will continue to work. Of course this requires that the file be located in the same folder as the project.
PUT /playback/cg_projects/{n}/items/{i}
Body:
{
	"moviePath" : url, REQUIRED eg. using full path "/Volumes/Movies/MyMovie.mov"
}

Change Images items

PUT /playback/cg_projects/{n}/items/{i}
Body:
{
	"imagePath" : url, OPTIONAL eg. using relative path "../MyImage.jpeg"
}

Change Audio items

PUT /playback/cg_projects/{n}/items/{i}
Body:
{
	"filePath" : url, OPTIONAL eg. using relative path "../MySound.AIFF"
}

Playlists

Get info about a playlist:

Here is an example of request that you can use in a simple browser, to get the information about the playlist {n}:

GET /playlists/{n}
Response: Playlist object

Playlist object:

{
	"unique_id" : string, name of the document made unique
	"path" : string, OPTIONAL eg. "/Volumes/Videos/MyPlaylist.xpls"
	"name" : string, eg. "MyPlaylist"
	"loop": boolean,
	"chain": boolean,
	"cue": boolean,
	"shuffle": boolean,
	"is_folder_based": boolean,
	"folder_based_path": string OPTIONNAL eg. "/Volumes/Videos/"
	"total_items" : number, eg. 57 OPTIONAL only if 'items' is not present
	"player_description" : string, eg. "Virtual Output (1080i 59.94)"
	"duration" : number, eg. 1800.7999
	"duration_string" : string, eg. "00:30:02" HH:MM:SS
	"preset_duration": number, eg. 1800
	"preset_duration_string": string, eg. "00:30:00" HH:MM:SS
	"start_time_offset": string, eg. "00:30:00" HH:MM:SS
	"enable_clocked_items": boolean,
	"is_front" : boolean,
	"has_on_air_item": boolean,
	"items": array <Playlist Item Object> OPTIONAL Pass "include_items=true" in query parameters
}

NOTE:
The "preset_duration" parameter is a theoretical value that indicates the desired duration of the playlist althougth the duration may or may not be equal to this one.


Get the playback status of a playlist

The following request will get the playback status of playlist {n}. You can use the playlist index, or a unique ID (see above).

GET /playlists/{n}/playing
Response: playback response object


Get the list of items of a playlist

The following request will get the list of items in playlist {n}. You can use the playlist index, or a unique ID (see above)

GET /playlists/{n}/items
Response: array playlist's item object


Get the list of items start times

It is usefull when you don't want to ask the whole playlist if a duration has changed
GET /playlists/{n}/items/start_times
Response: array playlist's item object


Get the list of items

Retrieve a list of items that doesn't match the "theoreticalStartDate" of the playlist
GET playlists/{n}/items/out_of_time_range_items
Response: array playlist's item object


Get the info of a specific item in a playlist

The following request will get the info of the item {m} in playlist {n}. You can use the playlist index, or a unique ID (see above), same thing for the clip, you can use either the index or the unique ID.

GET /playlists/{n}/items/{m}

Playlist's item object response:

{
	"unique_id" : string, OPTIONAL * eg. "666AD1EF-54C6-4A63-A67B-501C57E6080F"
	"name" : string, eg. "MyMovie1"
	"clip_type" : enum <
clip_type
>, "segment_number" : number, "reconcile_id" : string, OPTIONAL "isci_code" : number, OPTIONAL "url" : string, eg. "/Users/admin/Documents/MyMovie1.mov" for FILE or STREAM "video_codec" : string, eg. "H.264" "audio_codec" : string, eg. "AAC" "last_modification_date" : string, "has_in_point" : boolean, "in_point" : number, eg. 9.902 (in seconds) "has_out_point" : boolean, "out_point" : number, eg. 59.000 (in seconds) "closed_captions" : array <string>, OPTIONAL "languages" : array <string> OPTIONAL "live_source_name": string OPTIONAL eg. "Live Source 2" "is_streamed": boolean, Indicates if the stream is a remote file or not. "playback_mode" : string,
playback mode
"resize_mode": string,
resize mode
"duration" : number, eg. 679.902 (in seconds) "duration_timecode" : string, eg. "00:11:34" HH:MM:SS "frames_per_second" : number, "drop_frame" : boolean, "is_offline": boolean, will always set to false for a LIVE or STREAM clip. "is_valid" : boolean, "is_cued_as_next": boolean, "validation_status" : string,
validation status
"validation_error" : string,
validation error
"start_time" : number, "start_timecode" : string eg. "00:00:10" HH:MM:SS "has_absolute_start_time" : boolean, "displayed_start_time" : number, "displayed_start_timecode" : string, eg. "00:00:00" HH:MM:SS "theoretical_absolute_start_time" : number, eg. 13.532 (in seconds) "actions" : array <action>, "audio_volume" : number, "logo_enabled" : boolean, "logo_filename" : string, OPTIONAL "reverse_field_order" : boolean, "subtitles" : array <string>, OPTIONAL "start_transition_name": string eg. "Push - Down", "is_used_by_scheduler": boolean, "last_started_date": string }

* : if the unique_id property is not present it means that the item is still in the playlist but will be further deleted and thus cannot be accessed.
NB: If 'clip_type' is a comment item, he will only have 'unique_id', 'name', 'clip_type' & 'segment_number' properties.


Get an Apple script action of a playlist item

The following request will retrieve the action {k} set on the item {m} of playlist {n}. You can use indexes, or unique IDs (see above).

GET /playlists/{n}/items/{m}/actions/{k}

Action response object:

{
	"name" : string, eg. "Display Finder Message" -> name of the AppleScript
	"unique_id" : string, eg. 0650A319-B0B7-4B06-957C-F81B38470548
	"position" : number, eg. 0
	"position_type" : string, 
position type
"position_timecode" : string, eg. "00:00:00:00" HH:MM:SS:FF "parameter" : string, eg. Hello "is_outpoint_clamped" : boolean, "is_inpoint_clamped" : boolean, "is_valid" : boolean, "is_offline": boolean }


Get the thumbnails

Retrieve the thumbnails of all the clips in the playlist
GET playlists/{n}/thumbnails
Response: array playlist object

Retrieve the thumbnail of a clip (in JSON with Base64 data)
GET playlists/{n}/thumbnails/{i}
Response: array playlist's item object

Retrieve the thumbnail of a clip (in JPEG)
GET playlists/{n}/items/{i}/thumbnail
Response: JPEG


Check for missing clips / validate

The following request will validate the clips within a playlist. A validation will open the file, read the header to retrieve the codec and format. You can either ask it for the whole playlist, or for a specific clip in the playlist. You can use the playlist index, or a unique ID (see above), same thing for the clip, you can use either the index or the unique ID.

There are 2 types of check:

  • A "simple" validation, "check for missing clips": we will compare the modification date of the file, and what we have stored in the playlist, and only validate the clip if the 2 are different. This is mainly useful when asking a whole playlist to check if clips have been modified or became online/offline
  • A "forced" validation: we will not check the modification date and force to validate the clip. This is to be used with care as it uses some resources (we have to open the file to get its info).

Check for missing clips

For the whole playlist:

GET /playlists/{n}/validate
Response: command response object

For a specific clip:

GET /playlists/{n}/items/{m}/validate
Response: command response object

Force a validation

For a specific clip (it is not recommended to do it on a whole playlist as it will use resources):

GET /playlists/{n}/items/{m}/validate?force=1
Response: command response object


Update playlist's clip

All properties of a clip can be changed but here are the most common to be changed.
WARNING: if you change some properties that doesn't appear on this list, it might lead to unwanted UI behaviour. This command will also automatically save the playlist.
PUT /playlists/{n}/items/{m}
Body:
{
	"name" : string, OPTIONAL eg. "MyMovie1"
	"url" : string, OPTIONAL eg. "/Volumes/Movies/MyMovie.mov" (ONLY FOR FILE or STREAM)
	"live_source_name" : string, OPTIONAL eg. "Live Source 2" (ONLY FOR LIVE)
	"duration" : number, OPTIONAL eg. 679.902 (in seconds) (ONLY FOR LIVE or STREAM)
	"playback_mode" : string, 
playback_mode
OPTIONAL "has_in_point" : boolean, OPTIONAL "in_point" : number, OPTIONAL eg. 9.902 (in seconds) "has_out_point" : boolean, OPTIONAL "out_point" : number, OPTIONAL eg. 59.000 (in seconds) "start_transition_name": string OPTIONAL }
Response: playlist's item object


Change playlist content & properties

WARNING: You MUST send the entire items list, the content will be reflected, the additional items wil not be added nor removed. To add or delete items, please use POST/DELETE requests
PUT /playlists/{n}/items/


Update clip's action

PUT /playlists/{n}/items/{m}/actions/{k}
Body:
{
	"name" : string, OPTIONAL eg. "Display Finder Message" -> name of the AppleScript
	"position" : number, OPTIONAL eg. 0
	"position_type" : string, OPTIONAL
	"position_timecode" : string, OPTIONAL eg. "00:00:00:00" HH:MM:SS:FF
	"parameter" : string, OPTIONAL eg. Hello
}


Create an empty playlist

POST /playlists/{NAME}
Response: playlist object


Create a clip

POST /playlists/{n}/items

If you want to create a clip at a specific index {m}, you can use the following:

POST /playlists/{n}/items/{m}
Body:
{
	"clip_type" : enum <
clip_type
>, REQUIRED "url" : string, REQUIRED ONLY FOR FILE or STREAM eg. "/Volumes/Movies/MyMovie.mov" "live_source_name" : string, REQUIRED ONLY FOR LIVE eg. "Live Source 2" "duration" : number, REQUIRED ONLY FOR STREAM OR LIVE eg. 679.902 (in seconds) "name" : string, OPTIONAL eg. "MyMovie1" "playback_mode" : string,
playback_mode
OPTIONAL "has_in_point" : boolean, OPTIONAL "in_point" : number, OPTIONAL eg. 9.902 (in seconds) "has_out_point" : boolean, OPTIONAL "out_point" : number, OPTIONAL eg. 59.000 (in seconds) "start_time" : number, OPTIONAL }
Response: playlist's item object

Examples:

File based clip body:

{
	"clip_type" : 0,
	"url" : "/Volumes/Movies/MyMovie.mov"
}

Comment:

{
	"clip_type" : 3,
	"name" : "Start Section"
}

Live clip body:

{
	"clip_type" : 4,
	"live_source_name" : "Live Source 2",
	"duration" : 1800
}

Stream clip body:

{
	"clip_type" : 5,
	"url" : "rtmp://192.168.0.10:1935/live/mystream",
	"duration" : 1800
}


Create an action on a clip

POST /playlists/{n}/items/{m}/actions
Body:
{
	"name" : string, OPTIONAL eg. "Display Finder Message" -> name of the AppleScript
	"position_type" : string, 
position_type
OPTIONAL "position_timecode" : string, OPTIONAL eg. "00:00:00:00" HH:MM:SS:FF "parameter" : string, OPTIONAL eg. Hello }
Response: action response object



Applescripts

Get Apple script actions of a playlist item

The following request will retrieve the actions set on the item {m} of playlist {n}. You can use indexes, or unique IDs (see above).

GET /playlists/{n}/items/{m}/actions
Response: array <playback response object>


Get available Apple script action's names list

The following request will retrieve the available actions on the server. You can use them to update your clip's actions

GET /actions
Response: array <string>


Run an Apple script action on the go

The following request will run the mentionned apple script.

GET /actions/{name}/run?parameter={parameter}
Where :
{name} is the name of the action (the one you see on your folder)
{parameter} is the paramter you want to pass to that action

Warning: Use url percent encoded string if your action's name or parameter is using special characters (especially spaces) !

Response: command response object


DELETE requests can be used to delete elements, thus affecting your upcoming playback, use it with caution as it can not be reverted once done.


Delete a specific clip

DELETE /playlists/{n}/items/{m}
Response: command response object

NOTE:
Trying to delete a playing clip will not affect the playback and the UI directly. It will be deleted once the clip has ended.

Delete all clips of a playlist

DELETE /playlists/{n}/items
Response: command response object

NOTE:
Trying to delete all clips of playing playlist will return an error.

Delete a specific clip of a playlist

DELETE /playlists/{n}/items/{m}
Response: command response object

NOTE:
Trying to delete a playing clip of a playlist will return an error.

Delete all actions of a clip

DELETE /playlists/{n}/items/{m}/actions
Response: command response object

Delete a specific action

DELETE /playlists/{n}/items/{m}/actions/{k}
Response: command response object



Scheduler & Control

Start the schedule

GET /scheduler/start


Stop the schedule

GET /scheduler/stop


Get the list of playlists in the current schedule

GET /scheduler/playlists
Response: array <scheduler's playlist object>

Scheduler's Playlist object response:

{
	"path" : string, eg. "/Volumes/Movies/DailyPlaylist.xpls"
	"missing_clips" : number,
	"modification_date" : string, eg. "Today at 09:35"
	"is_folderbased" : boolean,
	"total_items" : number,
	"duration" : number, eg. 1802.00
	"duration_string" : string eg. "00:30:02" HH:MM:SS
}


Open a playlist from the schedule

The following request will open the playlist with specified path {path}. Once a scheduled playlist is open you can control it the way you do with opened playlists.

GET /scheduler/playlists?path={path}
Response: playlist response object in case of success, command response object in case of open failure


Close a playlist

The following request will close the playlist with specified ID.
Warning ! Use this command with care as some other remote user may no longer have access to the playlist after its close.

GET /playlists/{id}/close


Get schedule's infos

GET /scheduler?include_items=1

You can retrieve several infos about the current scheduler. The query parameter "include_items" will allow you to get all the events of the scheduler. If you don't need them, don't pass it.

Response:
{
	"version" : string, eg. "2.0"
	"is_enabled" : boolean,
	"schedule_path" : string, OPTIONAL eg. "/Users/admin/Documents/MySchedule.xml"
	"current_playlist": string, OPTIONAL
	"next_playlist": string, OPTIONAL
	"next_timed_playlist": string, OPTIONAL
	"events": array <scheduler event response object> OPTIONAL
}


Get schedule's events only

GET /scheduler/events

Scheduler's event object response:

{
  "playlists": [
	{
	  "playlist_path": string, eg. "/Users/admin/Documents/MyPlaylist.xpls"
	  "should_shuffle": boolean,
	  "should_loop": boolean,
	  "should_randomize": boolean
	},
	{
	  "playlist_path": string, eg. "/Users/admin/Documents/MyPlaylist.xpls"
	  "should_shuffle": boolean,
	  "should_loop": boolean,
	  "should_randomize": boolean
	}
  ],
  "is_enabled": boolean,
  "repeating_event_start_time": number, OPTIONAL
  "should_loop": false,
  "repeating_days": {
	"monday": boolean,
	"friday": boolean,
	"sunday": boolean,
	"tuesday": boolean,
	"thursday": boolean,
	"wednesday": boolean,
	"saturday": boolean
  }, OPTIONAL
  "display_name" : string,
  "is_repeating_event" : boolean
}

Resynchronize the schedule

The following request will ask the scheduler to resynchornize: stop playing what it is currently playing and start playing what was scheduled to play.

GET /scheduler/resynchronize
Response: command response object



Mediabrowser

Refresh media browser's content

GET /media/refresh
Response: command response object



For more information

If you need more info or support about OnTheAir Video, you can find it on our support desk. And if you need additional information on the API and/or the websockets, submit a ticket and we'll be happy to guide you.