Read a Linux screen's Presentation Network readiness
GET
/api/v1/screens/{id}/presentation-network
const url = 'https://example.com/api/v1/screens/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/presentation-network';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/screens/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/presentation-networkReadiness is server-derived from the assignment and the player’s reported helper, NetworkManager, Wi-Fi, revision, and connection facts.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters”id
required
string format: uuid
Responses
Section titled “ Responses ”Assignment and operator-facing readiness state
Media typeapplication/json
object
data
required
object
screenId
required
string format: uuid
platform
required
string
presentationNetworkId
string format: uuid
presentationNetworkName
string
assignedAt
string format: date-time
applicable
required
boolean
status
required
string
detail
required
string
helperState
string
networkManagerAvailable
boolean
wifiAdapterPresent
boolean
radioEnabled
boolean
reportedState
string
installedNetworkId
string format: uuid
installedRevision
integer format: int64
activeNetworkId
string format: uuid
lastConnectedAt
string format: date-time
lastFailureAt
string format: date-time
lastFailureCode
string
limitation
string
wiredInterfaceAvailable
boolean
wiredIpv4
string format: ipv4
credentialsAvailable
required
boolean
Example
{ "data": { "status": "not_applicable", "helperState": "ok", "reportedState": "unsupported" }}Screen is outside the caller’s scope
Screen not found