Broadsign Air Quick Start

This quick start provides a basic introduction to Broadsign Air. By following these steps, you will be able to add the "player" that represents your own player and generate a playlist.

Note: Any timestamps included in the playlists will use the timezone configured in Broadsign Control Administrator for the related Display Units. It is essential to ensure that the correct timezone is configured. If no timezone is set, the server will default to GMT+0 for the start and end date of campaigns, schedules, and opening hours under that Display Unit. Different Display Units can be set to different timezones if needed. For more information, see Timezone.

Note: For more information on the Broadsign Air configuration, see Configure Broadsign Air.

To get started with Broadsign Air:

  1. Request that Broadsign Air is activated on your domain. See Prerequisites.
  2. Once activated, create an API user in Broadsign Control Administrator and generate a REST API Token for it in Broadsign Control Administrator. See Add a User in Broadsign Control Administrator
  3. Schedule content (campaigns, ad copies, etc.) to your display units. See Add Campaigns.
  4. Add a player registration using a custom id in that display unit. See Add a Player in Broadsign Control Administrator.
  5. Note: Once you have registered the player, you must activate (promote) it with a playlist generation request using the player info.

  6. If you need different content playing in sync on multiple players using the generate v1 endpoint, set up a Display Unit Group. See Synchronized Players.
  7. Generate a playlist by calling this API with a curl command (see Sample Request Using Curl).
  8. There are two versions of the generate endpoint. The response will differ depending on the version used.

    • If you are using generate v1:
    • If you are using generate v2:
    • The generate v2 endpoint supports multiple frames playlists. See Multiple Frames Support for more details.

    • If you are using generate_long:
    • The generate_long endpoint allows Players to fetch offline playlists that are available for up to 14 days.

    Note: Some “0” values have been included in this example for sake of clarity. Actually, 0 values are omitted in the serialized output and are to be assumed as the default value. The default values of any other type used are also omitted from results ("false" for boolean values and "" for string values). This is done for performance and payload size reasons.

    Once promoted, the new player appears in Broadsign Control Administrator under the Players resource tab. For more information, see Players (Resource) in the Broadsign Control documentation.

  9. If applicable, confirm the Proof of Play (PoP) using the REST API token (see confirm_playback):
  10. Copy
    curl -X POST https://air.broadsign.com/playlist/v1/confirm_playback \
    -H 'Authorization: Bearer cbdbc369a063de6c0f458557f1456602' \
    -d '{
    "player_identifier": "abcd1234",
    "screen_identifier" : "1",
    "confirmed_items": [
      {
        "playlist_item_token":"CgphbGV4YW5kcmVjEgNVVEMaDAj22I7oBRCAhLjZASICCAUoAToDCNMBQgMIlRtKAwiSG2IDVVUwcgMI4BE=",
        "custom_data": { "ext1":"", "ext2": "" }
      }
    ]
    }'