BrightSign REST APIs (Landing Page)

Basic Authorization and Setup APIs

This block diagram describes how authorization and setup APIs communicate in the BrightSign system. It references bsn.cloud servers but also describes the workflow for BrightSignNetwork.com servers.

Authorization APIs

An OAuth (bearer) token gives users authorization to communicate with APIs and send requests to the B-Deploy or Remote DWS APIs.

• Use this API to get a Self token, which returns list of networks. Then, as an authenticated user, you can send a Full token to the correct network which allows you to access the network within the scope of what you are allowed to do. 
• This API returns either a valid token that gives you access to any version of the bsn.cloud APIs, or a valid token that gives you access to any version of the BrightSignNetwork .com APIs.
• The bsn.cloud and BrightSignNetwork.com base URLs are:
  • https://api.bsn.cloud/ 
  • https://api.brightsignnetwork.com/
    

Setup (Deployment) APIs

B-Deploy APIs are available through BSN.cloud for automated deployment of players in the field. These APIs deliver the setup to players and allow creation and modification of the setup packages. They consist of Provisioning Server and Provisioning Setup Server APIs:

• The Provisioning Server (PVS) returns an URL when given a serial number for any bsn.cloud or bsn connected device. The PVS provides only REST APIs.
• The Provisioning Setup Server (PSS) stores and serves setup packages, presentation packages and firmware updates. The PSS provides a UI (in addition to REST APIs), which makes calls to PVS to add and retrieve serial numbers and URLs. 

Player, Service, and WebSocket APIs

This block diagram describes how player, service, and WebSocket APIs communicate in the BrightSign system. It references bsn.cloud servers but also describes the workflow for BrightSignNetwork.com servers.

Player APIs

These APIs allow you to connect directly or indirectly to individual BrightSign players. These APIs are especially useful if there are many devices on the network so you can more quickly find and access players. Remote player APIs include the Remote DWS APIs and Local Web Server APIs, while the Local DWS APIs and the Presentation Autorun Server APIs are local player APIs:

• 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. These APIs also include WebRTC APIs and Local Web Server APIs.
• Local Web Server APIs let you access and modify user variables over a local network. 
• Local DWS APIs 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.
• Presentation Autorun Server APIs 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. 

Service APIs

The BrightSignNetwork.com and bsn.cloud APIs expose the functionality of our BrightAuthor and BrightAuthor:connected content management systems using a standard set of endpoints, entities, and methods. Developers can use these APIs to build custom content management interfaces with some or all of the features that we have developed for our own content management system. These APIs can also be used for device/fleet management.

BSN.cloud Main APIs allow users of our cloud-based infrastructure to interact with networked BrightSign players. Partners can use the BSN.cloud APIs with or without their own servers. 

BSN.com Main APIs use the older BrightSign network to interact with BrightSign players.

WebSockets APIs

The WebSockets APIs 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.