Diagnostic Web Server APIs

these apis allow you to connect to individual brightsign players they are especially useful if there are many devices on the network so you can more quickly find and access players local dws apis local dws apis docid 2zmel07w011h1267dt 59 let you access your players on a local network these apis give you information about the player, let you reboot the player, see the health of sd card, and access all of the functionality of the calls that underlie the dws in the brightauthor\ connected ui the local dws apis include presentation autorun server apis, which are hosted by the presentation autorun, and can be accessed with authentication from the local dws only brightscript objects in the presentation autorun know how to respond to these requests local dws apis are local player apis and are authenticated through a username and password, not an oauth bearer token remote dws apis the remote dws apis docid\ kku9e7f7chc5lwofxs9e0 are contained in the websockets docid 2foo6xeacvdg8em0fu6mq apis, which use the websocket connection to leverage legacy endpoints that would otherwise only be addressable via the local network once a connection is established, the brightsign websockets server can send 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 the remote dws apis allow you to access your player through bsn cloud (using the bearer token for bsn cloud) as well as get information about the player, reboot the player, see the health of sd card, and access all of the functionality of the calls that underlie the dws in the brightauthor\ connected ui wsapi v3 png