Postman Collections

https //archbee doc uploads s3 amazonaws com/0prk6so2dy9ldu77jb8d1/qwdrrumgr9xwqqy7s56fh bsncontrolpostman collection json https //archbee doc uploads s3 amazonaws com/0prk6so2dy9ldu77jb8d1/yl0q49l09ts1m0goztirp bsn control cloud productionpostman environment json bsn control (control cloud) library the postman library for bsn control allows you to quickly familiarize yourself with the different apis and processes associated with a bsn control subscription follow the below steps to create a person/network, create a player setup, and provision a player on your network with the player setup this is a collection of sample endpoint calls to introduce users to our infrastructure it is not a comprehensive document of our available endpoints please see the bsn cloud main apis docid\ goemci9nmvgakttr5qcjs , remote dws apis docid\ kku9e7f7chc5lwofxs9e0 , and b deploy/provisioning apis docid\ wccw4tqerzpxv7kjq a3p endpoint documentation for a complete list of those endpoints and their usage prerequisites a client id and client secret (provided by brightsign) postman the bsn control library collection and bsn control cloud production environment a brightsign player with an active internet connection steps screenshot 2024 01 05 at 11 30 43 am png import both the bsn control library collection and the bsn control cloud production environment into postman set the postman environment to bsn control cloud production using the dropdown menu in the top right select the "eye" icon and select edit to edit the following variables (other variables will get their values from postman scripts), as shown in the image above partneremail this email address, which should be the same as the partner login for now partnerfirstname your first name partnerlastname your last name networkname the name of the bsn cloud network to create this name must be unique within the bsn cloud database you can change this value later if you want to create multiple networks (for example, for different customers) clientid provided by brightsign clientsecret provided by brightsign playerserial the serial number of the player to provision on your bsn cloud network playermodel the model number of the player (for example, "xd1034") devicename the device name, which can be arbitrary setupname the player setup name, which can be arbitrary useraccesstokenlifetime the amount of time that a full access token for a network remains valid (the default is 15 minutes) go to bsn > user/self > post self select send to register with bsn cloud this call also returns your person credentials and an auto generated password, which postman will store verify your email address bsn cloud will send an email to your email address this may take a few minutes select the link in the email to verify the address you don't need to follow the additional steps to create a network since these steps will be performed using apis below select the token (self) call in the root of the library select send to get a "self" auth token, which postman will store go to bsn > user/self > post self/networks select send to create a bsn cloud network with your credentials as the network owner select the token (full) call in the root of the bsn control library select send the server will return a "full" auth token, stored in postman, which will give you access to the network you created to renew the "full" access token, repeat this step the default timeout for the token is 15 minutes select the token (device registration) call in the root of the bsn control library select send the server will return a "device registration" auth token, which postman will store the "device registration" token is separate from a user token and allows players to provision themselves for a certain network go to b deploy > post /setup/ select send to post a setup to the b deploy server and get the setup id, which postman will store go to b deploy > post /device/ select send your device serial number is now associated with the id of the device setup you created in the previous step power on or reboot your player the player will reboot several times while provisioning itself for your network go to bsn > devices > get devices select send to get a list of the players on your network go to remote dws > get /info/ select send to get player information