Data Partner Resources
      Back to home
      1. Knowledge Base and Documentation
      2. IRIS-enabled™ Contextual Data: Partners
      3. Data Partner Resources

      Data Partner Enrichment API Integration

      IRIS.TV Data Partner Enrichment integration works across two key API handshakes.

      Integration Overview

      Step 1: Receiving Video Data for Enrichment Processing

      IRIS.TV will send each video's metadata and video source URLs to contracted contextual data partners for processing.

      Videos will be sent via an HTTP Post with a JSON body. The source URL + billing ID is used as the identifier.

      Video metadata can include:

        • Title
        • Description
        • Length (seconds)
        • Source Keywords
          • Genre
          • Categories
          • Show
          • Episode
          • etc.
        • Thumbnail URL
        • Source URL (unique identifier)

          • .mp4, or

          • .m3u8 

        • Billing ID
        • Closed Caption URL
          • .txt,
          • .vtt, or
          • .srt
        • iris_id (if contracted to receive)

      JSON video asset metadata sample:

      {
        "source_url" : "https://demo.client.com/2020/02/11/1696087107539/18066_5-f1bce056_444291_5192.mp4",
        "title" : "Dr. Phil Says It All",
        "description" : "You Are A Loudmouth Bully,’ Dr. Phil Says To Guest",
        "length_secs" : 136,
        "thumbnail_url" : "https://demo.client.com/2020/02/10/18066_5_video_640x360-e44050dc.jpg",
        "source_keywords" : 
        [
         "behavior",
         "dad",
         "Psychologist",
         "talk",
         "News",
         "dr phil show",
        ],
        "billing_id" : 111,
        "closed_caption_url" : "https://demo.client.com/2020/02/10/18066_5-e13346aa.vtt"
      }

       

       

      Step 2 : Sending Contextual Segments to IRIS.TV

      Contextual data partners will send segments for each video to IRIS.TV to be stored and activated via IRIS.TV’s ad server integrations:

      1. Data segments are sent via an HTTP Post to IRIS.TV with a JSON body.
      2. The source_url + billing_id are used as the video identifier.

      sample curl statement

      curl -H "Content-Type: application/json" \
        --request POST \
        --data \

       '{
            "secret":"iris.tv will provide your secret key-it goes here.",
            "url":"https://demo.client.com/2020/02/11/1696087107539/18066_5-f1bce056_444291_5192.mp4", 
            "billing_id":111, 
            "segments":["segment_1","segment_2"]

         }' \ 

      https://fertilizer.iris.tv/iris_enrichment_notifications

      billing_id must be sent as an integer, NOT as a string.

       

      Resending Segmentation for Existing Assets

      Data partners can re-enrich an asset by resending the enrichment call for the combination source_url and billing_id.

      Re-enriched assets will overwrite the initial segments with the newest segments. 

       

       

      Contextual Segment(s) Activation

      IRIS.TV stores contextual data partners segments as 3rd party meta-data on each video's asset record in the IRIS.TV system.

      When a video is viewed IRIS.TV will send contextual data partner segments to the publisher's ad call in the form of a key value pair (KVP Segment ID).

      Data Partner Enrichment Health and Ad calls may be monitored using the IRIS.TV platform