rDWS Other Endpoints

Base URL for these endpoints: https://ws.bsn.cloud/rest/v1/

_________________________________________________________________________

DELETE /storage/{:device_name}/

Reformats the specified storage device

You must disable the autorun before reformatting the SD card on your device. To disable the autorun, use the PUT /v1/control/reboot with body parameter { “autorun”:”disable” }, as described in this section. This can also be done in the local DWS Diagnostics tab.

Segment

device_name string: The specified storage device (see this page for a list of available devices)

Request Body

fs string: The file system to use when reformatting a storage device. The default value of fs is "exfat".

Request Example

DELETE /rest/v1/storage/sd/?destinationType=player&destinationName={{deviceSerial}} HTTP/1.1
Host: ws.bsn.cloud
Authorization: Bearer {{UserAccessToken}}
Accept: application/json, application/vnd.bsn.error+json
Content-Type: application/json
Content-Length: 49

This is the example request body:

{
    "data": {
        "fs": "exfat"
    }
}

Response Example

{
    "data": {
        "result": {
            "success": true,
            "output": "Format completeted successfully.",
            "error": ""
        }
    },
    "route": "/v1/storage/sd",
    "method": "DELETE"
}

GET /re-provision/

Calling this endpoint will re-provision the player (in other words, the B-Deploy setup currently associated with the player will be downloaded, and the device will go through setup again). The BrightAuthor:connected UI feature that uses this functionality is Reprovision Player.

The re-provision process involves the following steps:

If the “networking” section of the player’s registry contains the access and refresh tokens, it is assumed that the player was previously set up for BSN.cloud. So BrightSign keeps some setup-related keys in the Networking section (see below) and deletes the rest of the registry entries. If the Networking section does not include access and refresh tokens, it will empty the whole Networking section, format the SD card, and reboot to try to provision the player.
BrightSign also sets the “deviceSetupComplete“ parameter in the “autorun” section to null, so that the player can set up again. This key is set to 1 only if the player was previously set up through the on-device setup option.
The code removes all files from the default storage device (this is almost always the SD card). You do not need to format the storage separately.
The player reboots, fetches the setup package from B-Deploy, and re-provisions itself.

Setup-Related Keys

Request Example

Response Body

success bool: True means that the operation succeeded and the player will reboot. False means that the operation failed.

Response Example

POST /snapshot/

Takes a screenshot of the current screen contents and saves it to storage. See Remote DWS APIs#RequestMessageFormat for the Query String Parameters.

Request Example

Response Body

remoteSnapshotThumbnail string: A snapshot image thumbnail in Base64 format
filename string: The name and path of the snapshot image file. Call GET /file/{:path} to retrieve the full-resolution image.
timestamp string: The date and time the snapshot was taken. The date/time is formatted as "yyyy-mm-dd hh:mm:ss <timezone>".

Response Example

PUT /custom/

Sends custom data to the player. The player in turn sends the data as a message (in JSON string format) on UDP port 5000, which can then be captured by the autorun.brs or a JavaScript application on the player.

Request Body

command string: The custom data to send
returnImmediately bool: A flag specifying whether the server should respond to the PUT request immediately (true) or wait on a response to the UDP message from the BrightScript/JavaScript application (false).

Request Example

This is the example request body:

Response Body

If the returnImmediately property is true, the server will return a success or error message. If the property is false, the server will wait for a response from UDP port 5000 on the player and send it as the response to the PUT request.

Response Example

GET /download-firmware/

Instructs the player to download and apply a firmware update.

Query String Parameter

url string: The public URL for downloading the firmware-update file.

Request Example

Response Body

success bool: A flag indicating whether the download was successful
reboot bool: A flag indicating whether the player will reboot when applying a firmware update

Response Example