One of the strengths of the Wurl API is the breadth of video programming we make available. Our API exposes content from 1000s of Internet-based video publishers (“Programming Sources”). Through our API, video service providers can create apps with discovery and search experiences that integrate a wide variety of video programming – all delivered under each operator’s own brand and user experience.
The Wurl API provides normalized metadata that simplifies our customers’ content integration. This frees application developers from the complexity of developing and maintaining back-end services to on-board, index and update the thousands of content sources available on the Internet.
Playback Metadata Types
Direct (Native Player)
Thousands of video Programming Sources in the Wurl Index provide us with metadata to enable playback in our customer’s native video players (e.g. a pay TV operator’s native video player on a STB). Because this method provides effortless, 1-click playback for consumers, video programming made available in this way consistently produces the highest view counts and viewer loyalty. AOL, Brightcove and Wochit are examples of Programming Sources that support playback in native players.
Direct (Custom Player from Programming Source)
Some video publishers provide their own custom player for video playback. This is a method that has evolved from “embeddable” players popular on the Web for the past decade. For video programming from these providers, Wurl’s metadata includes a snippet of code - typically an HTML
<video> element. Wurl customers use these snippets to enable playback in a browser or a WebView. YouTube, PopcornFlix and Dailymotion are examples of Programming Sources in our Index that require the use of their own custom player.
Some Programming Sources allow Wurl to index their content, but require the use of their own proprietary app for video playback. Examples include: Toon Goggles, i-Velozity, Netflix and Hulu. We use the term “link-out” to describe this playback method where we maintain complete descriptive metadata for a publisher’s content catalog, but our playback metadata contains a deep-link that launches the publisher’s app and automatically starts video playback. For our customers, Link-outs require the installation of each content provider’s native app or web app.
Note: This is an area where many Programming Sources change their rules quite frequently. For example, Netflix allowed Link-Outs until recently, but now requires special permission.
Some Programming Sources do not allow their content to be indexed and require the use of their own proprietary app for video playback and discovery. In these cases, the Wurl index includes metadata related to each app (including launch information), but does not include descriptive metadata or playback metadata related to any of the video programming. This is the approach that Netflix takes on STBs with most operators – allowing the Netflix app to be accessible, but not allowing Netflix programming to appear in any operator-controlled discovery experience.
Wurl API responses include a “Playback Array” containing all of the information a developer needs to enable video playback pursuant to the methods exposed by each Programming Source (as described above). See our Play a Video guide for more details.
For more information, here are some examples of Programming Sources that provide API's or SDKs for advanced integrations.
Many of the content publishers that do not use aggregators provide their content in an easily digestible syndicated format that plays well on native device players.
Don't hesitate to contact us at support for any questions regarding specific integrations.