Brightcove Integration

NetX's Brightcove integration allows you to quickly and easily upload any of the video files you have stored in NetX directly to your Brightcove account. In order to enable this feature, you will need to receive certain credentials from Brightcove as well as update your NetX instance's configuration files. 

Enable Brightcove integration

To enable Brightcove integration, you must first obtain your Brightcove Account number, your BC_Token, as well as your client_id and client_secret. You may also refer to Brightcove's official API documentation during this process.

Account number

To acquire your Account Number, log in to the Brightcove account you wish to associate with NetX and navigate to the Account Information tab, from the Admin tab in the top-right corner of your screen.

Your Account number should be the second value you see from your Account Information area; simply copy and paste this value somewhere you can refer to it later. 


Open the Developer Tools for your chosen browser and navigate to the Console tab. The example below uses Google Chrome, with the Developer Tools being accessed by right-clicking anywhere on the page and selecting Inspect

The code you will place in the Console tab is as follows: 

var cookiesArray = document.cookie.split(";"), cookiesObj = {}, i, tmpArray = [];
for (i = 0; i < cookiesArray.length; i++) {
tmpArray = cookiesArray[i].split("=");
if (tmpArray[0].indexOf('BC_TOKEN') > -1) {
cookiesObj.BC_TOKEN = tmpArray[1];
window.prompt("BC_TOKEN:", cookiesObj.BC_TOKEN);

Save the subsequent pop-up token value somewhere you can access it later.

Acquire client_id and client_secret

You will need both your BC_Token and Account ID in order to find the client_id and client_secret values for your account. Once you have acquired these, insert them into the following code, and run this through either the Terminal (Mac) or follow Brightcove's instructions to be able to run cURL scripts on your Windows machine. Record both the client_id and client_secret from the subsequent output and save these for later use. 

curl \
  --include \
  --header "Authorization: BC_TOKEN _YOUR_BC_TOKEN_HERE_" \
  --data 'name=ingest-profiles-api-client&maximum_scope=[{
      "identity": {
        "type": "video-cloud-account",
        "account-id": _YOUR_ACCOUNT_ID_HERE_
      "operations": [


    }]' \

Connect to NetX

  1. Make sure Media Services is enabled for your NetX site.
  2. In order to use your Brightcove account with NetX, you must use your credentials with the following XML, to be added to your mediaServices.xml file found at  $NETXHOME/netx/config/mediaServices.xml. If mediaServices.xml does not exist, add the file at /netx/config now.


you have saved your updated mediaServices.xml, a restart of NetX is required in order for your Brightcove integration to take effect.

3. To confirm your Brightcove integration, navigate to the Integrations tab of the Systems area; you should see a Brightcove field with a blue status toggle.

Using Brightcove and NetX

Once your instance has a valid Brightcove integration, you will be able to upload videos to your Brightcove account easily via the Share action on an individual asset. Simply right-click the asset you wish to add to your Brightcove feed, then select Publish. Choose Brightcove, then click Publish. Once loading has finished, your video will be available instantly upon a refresh of your Brightcove page. This action is not available from a selection of assets. 

No relationship is maintained between your NetX asset and Brightcove. No updates to the asset of any kind will be mapped to your Brightcove video after the initial upload.


Property Description

If this property is not set, published videos will make use of the authenticated Brightcove account's default Ingest Profile. That default profile can be bypassed by setting this property to the name of a different Ingest Profile.

Value options: text

Requires restart? No


 To enable the Integrations area, this property must be set to true.

Value options: true / false

Requires restart? No

Was this article helpful?
0 out of 0 found this helpful