GET /v1/video/:connector/output/:device/
Retrieves information about the specified video output.
Segments
connector: The current value is alwayshdmidevice: This value is0for single-output Series 5 players and all Series 4 and older players. The value can be0-3for the XC4055, which has multiple outputs, and0or1for the XC2055 and XT2145.
Request Example
The example request parameters and headers are set as follows:
:connectoris set tohdmi:deviceis set to0
GET /api/v1/video/hdmi/output/0/ HTTP/1.1
Host: {{playerIP}}
Authorization: {{DigestAuth}}
Accept: application/json |
Response Body
resolutionsresolutions[ ]: An array of information about the graphics, output, video resolution. Returns result values for height and width.edid_identity: Parses the above string in a JSON format for readability. Requires an HDMI output connected to the player and a display.edidstring: Returns the EDID read string of the display connected to the player. If power save is on, zeroes will be returnedstatus:audioBitsPerSampleint: The number of bits per audio sampleaudioChannelCountint: The number of audio channels in the outputaudioFormatstring: The format of the audio output. A "PCM" value indicates that the player is sending decoded output.audioSampleRateint: The audio sample rate (in hertz)eotfstring: The current electro-optical transfer function (EOTF) used by the display. The following are possible values:"HDR (GAMMA)"
"SDR (GAMMA)"
"SMPTE 2084 (PQ)"
"Future (BBC/NHK)"
"unspecified"
outputPoweredbool: A flag indicating whether the display device is on (i.e. RX powered)outputPresentbool: A flag indicating whether the HDMI output is connected to a display device or not.unstablebool: A flag indicating whether the display signal is unstable or stable
modes: List of all available video modes on the player.activeMode: Information about the active video mode on the playerbestModestring: The best video mode for the player. The HDMI connector must be attached because it gets details from EDID result.configuredMode: The configured video mode on the player. This can be different thanactiveMode.powerSaveStatusbool: This value indicates the power save status of the display connected to the player.
Response Example
|
Endpoints:
GET /v1/video/:connector/output/:device/edid/
Returns the EDID information from a compatible monitor/television connected to the video output.
Segments
connector: The current value is alwayshdmidevice: This value is0for single-output Series 5 players and all Series 4 and older players. The value can be0-3for the XC4055, which has multiple outputs, and0or1for the XC2055 and XT2145.
Request Example
The example request parameters and headers are set as follows:
:connectoris set tohdmi:deviceis set to0
GET /api/v1/video/hdmi/output/0/edid/ HTTP/1.1
Host: {{playerIP}}
Authorization: {{DigestAuth}}
Accept: application/json |
Response Example
result is the EDID string result
{
"data": {
"result": "00ffffffffffff004c2d0d050100000030120103801009780aee91a3544c99260f5054bdef80714f8111214081809500950fb3000101023a801871382d40582c4500a05a0000001e662150b051001b3040703600a05a0000001e000000fd00184b1a5117000a202020202020000000fc0053414d53554e470a2020202020016b020322f1469004050320222309070783010000e2000fe305030167030c001000b82d011d007251d01e206e285500a05a0000001e011d8018711c1620582c2500a05a0000009e8c0ad08a20e02d10103e9600a05a00000018000000000000000000000000000000000000000000000000000000000000000000000000000000ef00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
}
} |
GET /v1/video/:connector/output/:device/power-save/
Retrieves the power status of the monitor connected to the player.
Segments
connector: The current value is alwayshdmidevice: This value is0for single-output Series 5 players and all Series 4 and older players. The value can be0-3for the XC4055, which has multiple outputs, and0or1for the XC2055 and XT2145.
Request Example
The example request parameters and headers are set as follows:
:connectoris set tohdmi:deviceis set to0
GET /api/v1/video/hdmi/output/0/power-save/ HTTP/1.1
Host: {{playerIP}}
Authorization: {{DigestAuth}}
Accept: application/json |
Response Body
is_connectedbool: A flag indicating whether the monitor is connected to the HDMI output on the playeris_poweredbool: A flag indicating whether the monitor is on (for example, RX powered)enabledbool: A flag indicating whether power-save mode has been enabled on the HDMI/VGA output
Response Example
{
"data": {
"result": {
"is_connected": true,
"is_powered": true,
"enabled": false
}
}
} |
PUT /v1/video/:connector/output/:device/power-save/
Enables or disables power-save mode on the monitor connected to the player.
Segments
connector: The current value is alwayshdmidevice: This value is0for single-output Series 5 players and all Series 4 and older players. The value can be0-3for the XC4055, which has multiple outputs, and0or1for the XC2055 and XT2145.
Request Example
The example request parameters and headers are set as follows:
:connectoris set tohdmi:deviceis set to0
PUT /api/v1/video/hdmi/output/0/power-save/ HTTP/1.1
Host: {{playerIP}}
Authorization: {{DigestAuth}}
Accept: application/json
Content-Type: application/json
Content-Length: 51 |
This is an example request body that enables the power-save mode:
{
"enabled": true
} |
Response Example
{
"data": {
"result": true
}
} |
GET /v1/video/:connector/output/:device/modes/
Returns a list of all available video modes on the specified video output.
Segments
connector: The current value is alwayshdmidevice: This value is0for single-output Series 5 players and all Series 4 and older players. The value can be0-3for the XC4055, which has multiple outputs, and0or1for the XC2055 and XT2145.
Request Example
The example request parameters and headers are set as follows:
:connectoris set tohdmi:deviceis set to0
GET /api/v1/video/hdmi/output/0/modes/ HTTP/1.1
Host: {{playerIP}}
Authorization: {{DigestAuth}}
Accept: application/json |
Response Body
Returns an array of video mode objects, each of which contain the following parameters:
modeNamestring: The mode (for example, “1920x1080x60p”)colorDepthstring: The color depth of the video signalcolorSpacestring: The color space of the video signaldropFramebool: Whether or not the video timecode uses drop framefrequencyint: The frame rate of the video outputwidthint: The width of the video outputheightint: The height of the video outputgraphicsPlaneWidthint: The width of the graphics planegraphicsPlaneHeightint: The height of the graphics planeinterlacedbool: Whether or not the video output is interlacedoverscanbool: Whether or not the video output is using an overscan setting or notpreferredbool: Whether or not video is the preferred mode
Response Example
|
GET /v1/video/:connector/output/:device/mode/
Retrieves the current video mode on the specified video output.
Segments
connector: The current value is alwayshdmidevice: This value is0for single-output Series 5 players and all Series 4 and older players. The value can be0-3for the XC4055, which has multiple outputs, and0or1for the XC2055 and XT2145.
Query String Parameters
Each of these parameters delivers a different mode value:
bestint optional: If set to 1, this returns the best modeactiveint optional: If set to 1, this returns the active modeconfiguredint optional: If set to 1, this returns the configured mode
Request Example
The example request parameters and headers are set as follows:
:connectoris set tohdmi:deviceis set to0bestis set to1
GET /api/v1/video/hdmi/output/0/mode/?best=1
Host: {{playerIP}}
Authorization: {{DigestAuth}}
Accept: application/json |
Response Body
isAutoModebool: Whether the mode is set to “auto”namestring: The name of the video mode. Same asmode.modeNamebelow.widthstring: The width value of the video mode.heightstring: The height value of the video mode.framesstring: The frame rate value of the video mode.scanstring: The scan character value of the video mode.modeobject: The currently configured video mode on the video output with following parameters -modeNamestring: The mode (for example, “1920x1080x60p”)colorDepthstring: The color depth of the video signalcolorSpacestring: The color space of the video signaldropFramebool: Whether or not the video timecode uses drop framefrequencyint: The frame rate of the video outputwidthint: The width of the video outputheightint: The height of the video outputgraphicsPlaneWidthint: The width of the graphics planegraphicsPlaneHeightint: The height of the graphics planeinterlacedbool: Whether or not the video output is interlacedoverscanbool: Whether or not the video output is using an overscan setting or notpreferredbool: Whether or not video is the preferred mode
Response Example
{
"data": {
"result": {
"isAutoMode": false,
"name": "1920x1080x60p",
"width": "1920",
"height": "1080",
"frames": "60",
"scan": "p",
"mode": {
"colorDepth": "8bit",
"colorSpace": "rgb",
"dropFrame": false,
"frequency": 60,
"graphicsPlaneHeight": 1080,
"graphicsPlaneWidth": 1920,
"height": 1080,
"interlaced": false,
"modeName": "1920x1080x60p",
"overscan": true,
"preferred": false,
"width": 1920
}
}
}
} |
PUT /v1/video/:connector/output/:device/mode/
Changes the video mode on the player. You should first send a GET request to find the body parameters of this API, but only the modeName parameter is required.
Segments
connector: The current value is alwayshdmidevice: This value is0for single-output Series 5 players and all Series 4 and older players. The value can be0-3for the XC4055, which has multiple outputs, and0or1for the XC2055 and XT2145.
Request Body
A video mode object containing the following value(s):
modeNamestring required: The mode (for example, “1920x1080x60p”). See Supported Video Modes for a list of the possible valid strings for your playercolorDepthstring optional: The color depth of the video signalcolorSpacestring optional: The color space of the video signaldropFramebool optional: Whether or not the video timecode uses drop framefrequencyint optional: The frame rate of the video outputwidthint optional: The width of the video outputheightint optional: The height of the video outputgraphicsPlaneWidthint optional: The width of the graphics planegraphicsPlaneHeightint optional: The height of the graphics planeinterlacedbool optional: Whether or not the video output is interlacedoverscanbool optional: Whether or not the video output is using an overscan setting or notpreferredbool optional: Whether or not video is the preferred mode
Request Example
PUT /api/v1/video/hdmi/output/0/mode/ HTTP/1.1
Host: {{playerIP}}
Authorization: {{DigestAuth}}
Accept: application/json
Content-Type: application/json
Content-Length: 95 |
This is the example request body:
{
"name": {
"modeName": "640x480x60p"
}
} |
Response Body
The server will return a success or error message. A successful response will almost always cause a reboot which will be indicated in the response.
successbool: Whether or not the operation was successfulrebootbool: Whether or not the player is rebooting
Response Example
{
"data": {
"result": {
"success": true,
"reboot": true
}
}
} |