Public | Automated Build

Last pushed: 2 years ago
Short Description
100 characters is too short.
Full Description

#UPP Brightcove Notifier

Receives Brightcove video notification events. Fetches video model, then creates UPP publish event and posts it to the CMS-Notifier.

##Build & Run the binary

export BRIGHTCOVE_AUTH="Basic YjY..."
export BRIGHTCOVE_ACCOUNT_ID="47628783001"
export CMS_NOTIFIER=""
export CMS_NOTIFIER_HOST_HEADER="cms-notifier"
export CMS_NOTIFIER_AUTH="Basic dXB..."
go build; ./brightcove-notifier

Look for the auth values in LastPass' UPP Shared Folder.


  • /notify

POST endpoint (registered with Brightcove CMS Notifications API)

  • /force-notify/{videoID}

POST endpoint (useful for forcing video model publishes)

  • /__health

GET endpoint (FT standard)

  • /__gtg

GET endpoint (FT standard)




    "timestamp": 1423840514446,
    "account_id": "421252784301",
    "event": "video-change",
    "video": "4144892532001",
    "version": 26


curl localhost:8080/notify -X POST -d @videoEvent.json -i

Sometimes it's handy to test against the Brightcove Notifications API directly.
To create a public endpoint the most easy way is to deploy your app in Heroku.
Assuming you have an account create the Procfile and run godep:

  1. echo "web: brightcove-notifier" > Procfile

  2. godep save ./...

  3. Commit your changes, then push to heroku

Now you have a public endpoint, you can use the FT Development account to register this endpoint with Brightcove Notifications API. Once you've done with testing, please unregister your endpoint from Brightcove.

##Brightcove Integration

###Obtain Client Credentials

curl -i -XPOST \
   -H"Authorization:Basic ..." \
   -H"Content-Type:application/x-www-form-urlencoded" \
   -d"grant_type=client_credentials" \

you get an access token that you can use for a few minutes:

  "access_token": "AK5366ogmVGB-eix...",
  "token_type": "Bearer",
  "expires_in": 300

###Register notify endpoint with Brightcove Notification API

Let's say your client_id is 2221711291001. You could check your subscriptions:

curl -i \
  -H "Authorization:Bearer AK5366ogmVGB-eix..." \

It will give you a response like:

    "service_account": "2221711291001",
    "id": "5e831b0d-9d45-43b1-9464-86421e0feb4d",
    "events": "video-change",
    "endpoint": ""
    "service_account": "2221711291001",
    "id": "c456f1c2-f682-4a56-a276-93eab2075e87",
    "events": "video-change",
    "endpoint": ""
    "service_account": "2221711291001",
    "id": "7492891d-f012-46af-b571-060ae180bfbe",
    "events": "video-change",
    "endpoint": ""

Then you can create a new subscription:

curl -i -XPOST \
  -H "Authorization:Bearer AK5366oD..." \
  -H"Content-Type:application/json" \
  -d'{"endpoint":"", "events":["video-change"]}' \
  "service_account": "2221711291001",
  "id": "a35aa9c7-cefa-40dd-9222-e7216bccfa13",
  "events": [
  "endpoint": ""

Check your subscriptions again.

###Integration points

List of used Brightcove API endpoints (please keep this list updated):

  1. Get Video by ID
  2. Get Video Count - used in healthcheck
  3. Creating notification subscription - called once, manually, before deployment
  4. OAuth API Renewing Access Token


Read more on Brightcove API:

  1. CMS Notifications API Guide
  2. CMS Notifications API Reference
  3. CMS Video API Reference
  4. OAuth API Overview
  5. OAuth API Getting Client Credentials
  6. OAuth API Getting Access Token
Docker Pull Command