pybrightsign 0.1.7

Python module to simplify using the BrightSign BSN/BSNEE API.

pybrightsign

Python module to simplify using the BrightSign BSN/BSNEE API.

NOTE: this is early work in progress - interfaces subject to radical changes

Install with pip as usual:

pip install pybrightsign

Introduction

This library abstracts away authorization details and Upload API details, leaving the developer free to use the APIs directly and at as low a level as one would if using just the requests library without a bunch of boilerplate code.

Here is an example of using the Devices endpoint to show a list the names of all devices in a network:

from pybrightsign import Server

creds = {
    'network': 'Demo',
    'username': '[e-mail]',
    'password': 'swordfish'
}

# First create a server object using the domain name of your BSNEE instance
bsnee = Server('brightsign.example.com')
bsnee.authorize(creds)

# Now use the server's requests object as you would normally, 
# without worrying about api version, tokens, url prefix, basic headers, etc.
response = bsnee.requests.get('/devices')
response.raise_for_status()

devices = response.json()['items']

for device in devices:
    print(device['name'])

Even more powerful is the abstraction of the Upload endpoint, for example uploading a video and an image (to a particular folder), then uploading a web site (including the index.html and all css, js, images, etc. in the same folder):

from pybrightsign import Server

creds = {
    'network': 'My BSN Network',
    'username': '[e-mail]',
    'password': 'swordfish'
}

bsnee = Server('brightsign.example.com')
bsnee.authorize(creds)

bsnee.upload_file('promo.mp4')
bsnee.upload_file('logo.png', r'\Shared\Images')
bsnee.upload_web_folder('./website/index.html')

Methods

Constructor

To construct a Server object you need a valid domain name of the BSN/BSN.Cloud instance. The following constructor examples all begin with:

from pybrightsign import Server
domain = 'brightsign.example.com'

NOTE: If you are following along, please replace brightsign.example.com with your domain name or these examples will fail.

Minimal

The most basic construction uses only the domain name - which is required.

server = Server(domain)

This assumes the API subdomain is api and all calls to the API will begin with 'https://api.brightsign.example.com'. You can confirm this (and the API version) like this, for example:

>>> print(server)
https://api.brightsign.example.com/2019/03/REST

API Subdomain

If your API is located in a different subdomain than api, you can specify it like this

server = Server(domain, api_subdomain='apitest')

Now all API calls will begin with 'https://apitest.brightsign.example.com'

API Version

Although optional, if you know the API version you should specify it. If you do not the constructing a Server object prints the following warning:

WARNING: api_version (None) is invalid for https://api.brightsign.cri.com.  Attempting to discover correct api_version. This may take several seconds. To remove this warning (and this delay), please supply a valid api_version.

API versions are in the form of YYYY/MM . The constructor tries to discover the API version by first checking the known versions (from most recent to oldest). If a valid version is not found, it then tries the current year and current month, and keeps trying the previous month until it either finds a valid version or reaches the oldest known version (no point trying beyond that). This is handy if you do not know the version, but clearly this takes time that can be avoided if you tell it the version.

server = server(domain, api_version='2019/03')

Authorize

Once you have constructed a Server object (using any of the means above), you must authorize it before making calls. Create a dictionary with your credentials and pass it to the authorize() method.

creds = {
    'network': 'Demo',
    'username': '[e-mail]',
    'password': 'swordfish'
}
server.authorize(creds)

You can use the server object to see where you are connected any with which user:

>>> print(server)
https://api.brightsign.example.com/2019/03/REST as Demo/[e-mail]

Requests

Once authorized, you can now use the server's requests object. Use this exactly as you would a regular requests object except

• you don't have to manage the auth token, nor create a headers dict with the token.
• you don't have to use a full URL - only the endpoint path. For example, instead of using https://api.brightsign.example.com/2019/03/REST/contents you can simply use /contents
• Default headers
  • By default all request have Accept: application/json in the headers,
  • In the case of POST, PUT, or PATCH will also have Content-type: application/json
  • If you need different Accept or Content-type headers - or if you need additional headers, pass a headers dict as you normally would. It will get merged into the managed headers (i.e. the one that has the token)

Examples will make all of this clearer:

Let's say you want to POST a presentation. Using only requests you would do something like this (assuming you had created the get_presentation() and get_token() methods)

token = get_token()
presentation = get_presentation()  # returns a JSON string of the presentation to POST
headers = {
    'Accept':  'application/json',
    'Content-type': 'application/json',
    'Authentication': f'Bearer {token}'
}
response = requests.post('https://api.brightsign.example.com/2019/03/REST/presentations', data=presentation, headers=headers)

With pybrightsign you don't need get_tokens(), and your code would look like this (after the server object was authorized):

presentation = get_presentation()
server.requests.post('/presentations', data=presentation)

If you wanted a list of devices in XML insetead of JSON, you can override the Accept: header like this:

reponse = server.get('/devices', headers={'Accept': 'application/xml'})

You can stop reading here and you will have the full power of BrightSign APIs as your disposal. There are some utility methods which make some routine tasks a bit simpler. Each of these can be done with just the server's requests, but why would you?

List Networks

To see which networks you have access to you could use server.requests.get('/self/networks'), iterate through the response json items array and pull out the name field of each object. Or use get_network_names()

>>> server.get_network_names()
['admin', 'Demo', 'OtherNetwork']

Switch Networks

If you are authorized on one network, you can easily switch to a different network without having to re-authorize:

>>> server.switch_network('OtherNetwork')
>>> print(server)
https://api.brightsign.example.com/2019/03/REST as NewNetwork/[e-mail]

Move a device

To move a device from one group to another:

server.move_device_to_group(device_id, new_group_id)

Upload a file or a Website

To upload a file, you could wrestle with the Upload endpoint, or just use upload_file()

server.upload_file('./img/logo.png')

You can optionally specify which folder (virtualPath) to upload to:

server.upload_file('./img/logo.png', '\\Shared\\Images')

Backslashes in the virtualPath must be escaped with backslashes. Or use python's r-string notation (raw string)

server.upload_file('./img/logo.png', r'\Shared\Images')

Similarly, to upload a Website, point to the path/name of the site's index file. This will upload the index file and all other files in the same folder and its subfolders:

For example, if your website is a set of files like this:

my-site
│   index.html
│
├───css
│       style.css
│
├───img
│       background.jpg
│       logo.png
│
└───js
    ├───app
    │       ui.js
    │       
    └───utils
            api.js
            tools.js

You upload this folder with the name 'MySite' (for example) like this:

server.upload_web_folder('MySite', './my-site/index.html')

Replace index.html with the actual site's entry page is (e.g. default.htm )

...more to come...