The Broadsign Air API allows developers to generate a playlist.
The Broadsign Air API supports an HTTP authentication token that is included in the “Authorization” header of the HTTPS requests to the REST API, as defined in RFC 7235.
If a player is requesting more than once per minute, they will receive a
429 Too Many Requests.
The client receives a playlist of the requested duration (or one hour if the duration is not specified). If the playlist consists of Broadsign Reach bids, only the first 10 minutes of that returned playlist have executed bids in Broadsign Reach and filled any returned slots.
The bulk of the playlist is generated in advance, cached, and refreshed periodically. Subsequent requests from other players in the same venue will be fed from the cached playlist to ensure proper synchronization.
The playlist service cannot issue bids to Broadsign Reach for players that are not checking in. For multiple players in the same venue, a bid will be sent only once for a given slot, regardless of how often the players request the playlist.
For Broadsign Reach-integrated demand sources, bids are managed transparently for the first 10 minutes of playlist items. If ads are found, they are inserted. If not, the playlist follows the defined rules for priority campaigns, filler, and eventually, replaced with nothing at all, resulting in over-performance of direct-sold campaigns.
For the remainder of the playlist, all Broadsign Reach slots are skipped and filled instead with lower priority content or filler, following the same waterfall as if a bid was issued but there was no response.