Remote DWS APIs

the remote dws allows you to view and modify settings on a brightsign player over the internet the remote dws api is a rest framework that allows a client application to integrate with remote dws functionality the client application makes rest calls to the brightsign websockets server, which in turn sends websockets messages to brightsign players depending on the operation, the brightsign player may return information to the brightsign websockets server, which will be relayed in the server rest response to the client application rest urls the base url of the remote dws api is https //ws bsn cloud/rest/v1/ https //ws bsn cloud/rest/v1/ please note that the rest section is case sensitive and the server may return code 404 if the case is not matched exactly authentication all remote dws api calls require a valid oauth2 access token which maybe issued either to a user or to the client application the target player must belong to the same network for which the token has been granted please follow the 2025 api usage guide docid\ hbyhyv8svq0u6bzhuv50 to register your applications and obtain access tokens which grant access to the remote dws api request headers you should include the following request headers in your request the content type header is only needed when content is being sent in post or put api calls headers { 	'accept' 'application/json, application/vnd bsn error+json', 	'authorization' 'bearer {{useraccesstoken}}', 	'content type' 'application/json', } request message format http requests to remote dws resources must be json formatted and contain the following url parameters destinationtype string string the device type the only currently accepted value is "player" destinationname string string the device serial number requests that require a json body need to have an outer data object for instance, if a route expects enabled bool bool then the full json body would look like { "data" { "enabled" false } } some requests also require resource specific properties in the url or request body, as detailed in the url parameters and request body sections below response message format the server will respond to a rest request with a success or error message, which may also contain resource specific properties, as detailed in the response body sections below returned json objects will have an outer object containing the methods below, where data is an error or a result object containing the returned values route string string the route the request was sent to method string string the request method data object object the returned data for example { "route" "/v1/info", "method" "get", "data" { "result" { "model" "ls424" } } }