Integrating Your CMS with Video Cloud

Video Cloud
API Developer
CMS Integrations
Dynamic Ingest API
Player Management API

In this topic, you will learn the basic operations involved in integrating Brightcove Video Cloud with a CMS. It lists typical functions that users perform within the CMS and the Brightcove API operations that can be used to provide that functionality.

User functions

Below are functions related to Video Cloud that you might want to provide users of your CMS:

  • Add new videos to Video Cloud
  • Replace a Video Cloud video with a new version
  • Update metadata for videos, such as the title, description, and tags
  • Delete videos
  • Create playlists
  • Change the videos in a playlist
  • Delete playlists
  • Create video players
  • Modify video player properties, such as dimensions or styling
  • Add special functionality to video players through plugins
  • Publish single videos or playlists
  • Provide analytics data on video loads, views, play-rates, engagement, etc.

You may not wish to expose all this functionality to your end users - you may not want to let them delete videos, for instance. One of the advantages of integrating Video Cloud with your CMS rather than letting users go directly to Video Cloud Studio is that you can choose exactly what functionality to expose to users through the Brightcove APIs.


For all Brightcove API requests, authentication is based on OAuth2 access tokens. There is a two-step process for obtaining access tokens:

  1. Create client credentials with permissions for the API operations you need
  2. Use the client credentials to create a temporary access token to authenticate an API request

Creating client credentials

Creating client credentials is a one-time operation that can be performed through Video Cloud Studio or the OAuth API. However you do it, a client_id and client_secret are returned, which you must save to request access tokens.

Creating an access token

Temporary access tokens are created using the OAuth API. The client_id and client_secret must be BASE64-encoded and passed as a Basic Authorization string.

The access_token returned is in turned passed in an Authorization header with the API call:

>Authorization: Bearer your_access_token

Access tokens are valid for 5 minutes. Unless you are performing some kind of batch operation that will be making hundreds of successive API calls, it makes sense to just request a new one for each API call rather than trying to keep track of the timeout.

Adding Videos

If you wish to let users add videos to Video Cloud from your CMS, you can do that using the Dynamic Ingest API. We recommend that you have users upload videos to your repository, which could be an S3 bucket or just a public-facing server. The Dynamic Ingest system can pull in the videos and add them to the Video Cloud system through a two-step process outlined below.

Adding a video object to Video Cloud

The first step is to create a video object in the Video Cloud system by making a POST request to the CMS API:

The request body will include basic video properties in a JSON object - minimally, the video name, but you can also include additional metadata such as a description and tags:

"name": "Woodpecker",
"description": "A bird that hunts insects inside wood",
"reference_id": "Bird_Woodpecker.mp4",
"tags": ["bird", "air", "nature"]

Ingesting the video

When you create the video object, the CMS API will return a JSON object containing the video properties. You will extract the video id from the JSON, and use it to make a call to the Dynamic Ingest API to request ingestion and transcoding of the video:

Again you will send JSON in the request body specifying the location of the video file:

  "capture-images": true

The profile here is the Ingest Profile that specifies what renditions should be created in the transcoding process. In most cases, one of the following standard profiles should be adequate:

Dynamic Delivery profiles

  • multi-platform-extended-static
  • multi-platform-standard-static

Legacy ingest profiles

  • videocloud-default-v1 (the default)
  • screencast-1280
  • smart-player-transition
  • single-bitrate-high
  • audio-only
  • single-bitrate-standard
  • high-resolution

However, you can create additional custom ingest profiles, if needed, using the Ingest Profiles API or using Video Cloud Studio.

Adding poster and thumbnail images

The capture-images option in the code above instructs Video Cloud to capture poster and thumbnail images for the video at the mid-point during the transcoding process. Alternately, you can set capture-images to false and ingest images instead, either at the same time that you ingest the video or later:

"capture-images": false,
"poster": {
"url": "",
"width": 640,
"height": 360
"thumbnail": {
"url": "",
"width": 160,
"height": 90

See Images and the Dynamic Ingest API for more details.

Adding text tracks for captions or chapters

You can also use the Dynamic Ingest API to add text tracks in WebVTT files to videos, either at the time of ingestion or later. Text tracks are used to add captions or chapters to a video.

"capture-images": false,
"poster": {
"url": "",
"width": 640,
"height": 360
"thumbnail": {
"url": "",
"width": 160,
"height": 90
"text_tracks": [
"url": "",
"srclang": "en",
"kind": "captions",
"label": "English",
"default": true

See Ingesting WebVTT Files for more details.

Managing Videos

The CMS API allows you to get back video data for an account. (As shown above, it is also used to create video objects as part of the video ingestion process.) The most basic request is as follows:

By default, this request returns a JSON array of 20 video objects containing a wealth of metadata, including the name, description, tags, custom fields, the dates it was created and last modified, URLs for the poster and thumbnail, and much more.

You can refine the results of the request by adding one or more of the following parameters to the request:

this determines the number of video objects to return, and can be set to any number up 100 - the default is 20
this determines the number of items to skip, and so is used together with limit to page through the video catalog - the default is 0
this determines the video metadata field to sort the result by - by default, results are sorted by updated_at (descending, to show the most recently updated videos first)

See CMS API Overview - Parameters for detailed information on these parameters.

Searching for videos

You can also search for videos by a wide range of criteria using the q parameter. You can search by specific fields such as name, description, and tags, as well as dates and the status of the videos:,mammal

For details and all the options for searching, see Search for Videos.

Getting and updating a specific video

To retrieve a specific video by its id or reference id:

A GET request returns the video object. To update it, modify the JSON and return it using a PATCHrequest to the same URL.


Playlist information is also managed using the CMS API in much the same way as video information. Note that Video Cloud supports eight types of playlists in two categories:

Manual (or EXPLICIT) playlists
contain a specified set of videos - up to 100 videos may be included
Smart playlists
built dynamically at runtime based on search criteria - there are seven varieties of smart playlists corresponding to the way the videos are ordered within the list:

The limit on the number of videos can be set to any number up to 100.

As with videos, you can retrieve all playlists, using limit and offset to page through results if the account has a large number of playlists:

The returned array of playlist objects will include metadata for the playlist, including the type corresponding to the one of the types described above. If the type is EXPLICIT, there will also be a video_ids array containing the ids of the included videos. If the type is one of the smart playlist types, there will be a search property containing the search string that retrieves the videos, something like this:


You can also retrieve a single playlist by its id:

If you need to retrieve the full video objects for a playlist (to display information about the videos on a page), you simply add /videos to that URL:

Note that for a smart playlist, the request will return the videos that match the search criteria presently, but that may change.

Creating Players

Brightcove players can be created via the Player Management API. The API allows you to create players, update their properties, and get the embed code in the form of a URL, an iframe tag, or a block of HTML to embed in the page.

You can up to 200 players per account, but it is generally less confusing to users to have as few players as you absolutely need. You should have separate players for playing single videos or playlists, but otherwise you only need different players when they will be styled differently or have different functionality added through plugins.

To create a player, you simply make a POST request to the Player Management API:

In the body of the request, include the player configuration - the only thing required is a name:

"name": "Single video player for blog posts"

The response will give you the player id, as well as the embed code in multiple forms:

"embed_code": "<iframe src='//' allowfullscreen webkitallowfullscreen mozallowfullscreen></iframe>",
"embed_in_page": "",
"id": "de055fa4-4f09-45af-8531-419c6794ad04",
"preview_embed_code": "<iframe src='//' allowfullscreen webkitallowfullscreen mozallowfullscreen></iframe>",
"preview_url": "",
"url": ""

To get the full player configuration, you make a request to the /players endpoint, but add the player ID that is returned in the response above:

You can make a PATCH request to same endpoint to update the player configuration.

You'll notice in the response above, the preview_embed_code and preview_url. To allow testing of new players or player updates, newly created or updated players are set in preview mode to allow you to see it before pushing changes out to existing players. To push changes into production, you need to publish the player with this request:

Customizing Players

The Brightcove player is built with standard web technologies: HTML, CSS, and JavaScript. You can customize the player using those same technologies. This can be done in the page where the player is published, but best practice is to add your customizations to the player itself through the player configuration, updating the player via a PATCH request to the Player Management API as explained in the previous section.

You can also add additional features and functionality to the player through JavaScript plugins, and there is an extensive Player API to help you integrate your code with the player. Brightcove offers a number of ready-made plugins for such things as enabling advertising, customizing the endscreen, and adding overlays.

Publishing Videos

In the Creating Players section above we saw that when you get the player configuration object using the Player Management API, the returned data includes an iframe tag for embedding the player in an HTML page, and also a URL for the full HTML if you want to embed the player directly in a page.

For whichever embed you choose, you will need to add a Video Cloud video id or playlist id to the embed code to add content to the player. The iframe embed code looks like this:

allowfullscreen webkitallowfullscreen mozallowfullscreen></iframe>

To the URL for the player, you need to append the parameter videoId={}video_id, so that the full embed code will look like this:

allowfullscreen webkitallowfullscreen mozallowfullscreen></iframe>

If this is a playlist player, you use the parameter playlistId={playlist_id} instead. The modification of the in-page embed code is similar.

Unless the player dimensions are fixed in the player configuration, you will also need to size the player by adding width and height in a style attribute:

allowfullscreen webkitallowfullscreen mozallowfullscreen

Getting Analytics Reports

The Analytics API allows you to generate realtime analytics reports by:

You can specify the date range for the report, the metrics to return, and you can get the data in JSON, csv, or xlxs format

For periods within the last month, you can also generate detailed Engagement Reports that show views for every one hundredth part of the video.

Summary of APIs

Here is a summary of the APIs useful for integrating with Video Cloud.

Used to create client credentials and access tokens to access the other APIs.
Media Management
Ingest Profiles API
Used to create custom ingest profiles specifying the renditions to be created for videos added to Video Cloud
Dynamic Ingest API
Used to add videos and related media assets to Video Cloud
Used to create video objects for ingestion, and to manage videos and playlists
Brightcove Players
The Brightcove Player
The player includes a JavaScript API to interact with the player at runtime
Player Management API
Used to create and configure players, and to get the player embed code
Analytics API
Used to obtain analytics reports on video performance