...

• client_token: Authentication string associated with each client. This will be provided by IRIS.TV once the content feed is imported.

• platform_id: The reference ID for the video asset from the publisher’s CMS.

• access_token: Token used to authenticate with the IRIS.TV API. This will be provided by IRIS.TV once the content feed is imported.

Building the Integration

The order of operations for retrieving the context or category information should be as follows:

1. Call the IRIS.TV Context API call to retrieve context and category information on contextual segments for the next asset in the queue.

2. Add the context segment to the pre-roll ad tag for that video asset.

This process should be repeated as you iterate through the video playlist.

Formatting the API Call

The API call requires the client token, platform id, and access token. The client and access tokens will be provided after the initial ingest.

A sample of the Context API call:

https://context.iris.tv/video_info?access_token=90814301lkjafalkj&client_token=PAJEU091&platform_id=6026444633001

...

• iris_id : the asset’s current iris_id (hashed IRIS.TV Content ID).

• iris_id_expires_at : the UNIX Unix epoch timestamp when the current iris_id will expire.

• context : contextual segments for the asset

A sample of the Context API response:

{
  "success": true,
  "video_info": {
    "iris_id": "iris_098eiman91",
    "context": [
      "context_1", 
      "context_2", 
      "context_3"
    ],
    "iris_id_expires_at": 1588636800
  }
}

Note: The Context field will be used for all IRIS.TV Contextual Video Marketplace workflows.

After the Integration is Complete

Once the integration is complete and you’re receiving contextual segments, move on to Activating Contextual Data in order to add the data into your existing ad workflow.