On This Page

Player Management API Sample: Using last_viewed Data

In this topic, you will learn about reports using the player's last_viewed data.

Disclaimer

This sample app is meant as a way for you to explore the basics of the Player Management API. It is not meant to be an enterprise ready, deployable app. For instance, form validation is not exhaustive and passwords are sent NOT using HTTPS.

To learn about the general approach concerning the architecture of this sample app, specifically authentication and AJAX implementations, see the examples that use HTTPRequest.

Understanding last_viewed information

Each player has associated with it an array that contains a record of how many times a player was loaded. This information is stored in an array name last_viewed. You see below an example of such an array. Note that the count records how many time in the day the specific player was loaded. The date specifies the specific day.

Proxy code

In order to build your own version the sample app on this page, you must create and host your own proxy. (The proxies used by Brightcove Learning Services only accept requests from Brightcove domains.) A sample proxy, very similar to the one we use, but without the checks that block requests from non-Brightcove domains, can be found in this GitHub respository. You will also find basic instructions for using it there, and a more elaborate guide to building apps around the proxy in Using the REST APIs.