Notable contents of this release include a new JSON API for integrating Ooyala IQ with third-party players and Roku devices.
Software Feature Releases
New Ooyala IQ JSON API for Third-Party Players
We have updated the Ooyala IQ backend to support a JSON API endpoint. JSON is a lightweight open-standard data interchange format that is language independent, making it easy to read and write.
Use the new Ooyala IQ JSON API to communicate your third-party player's events to Ooyala IQ. You can use this endpoint to send JSON data to Ooyala IQ or you can use one of the out-of-the-box SDKs. For this release, we are offering an out-of-the-box SDK for Roku.
For more details on the Ooyala IQ JSON API, see Integrating Third-Party Players with IQ Using the JSON API.
New Ooyala IQ SDK for Roku Integration
You can now integrate Roku channels with Ooyala IQ with the Ooyala IQ SDK for Roku. The Ooyala IQ SDK for Roku is an out-of-the-box SDK that sends JSON data to the Ooyala IQ JSON API endpoint and automatically follows the best practices for what events should be sent when, and makes sure that all required fields are present.
The Ooyala IQ SDK for Roku supports the Roku OS v7+.
If you use the Ooyala IQ SDK for Roku, Roku will appear as an OS in the Device panel of the Ooyala IQ Business Intelligence interface.
The Roku player will appear in the Player panel as well.
Enhancements to the Ooyala Ingestion Service (OIS)The Ooyala Ingestion Service (OIS) v2.5 represents a major step forward for uploading videos and metadata into Backlot. OIS v2.5 makes it easier for users to ingest files into Backlot using FTP, Aspera, or MRSS.
What’s New in OIS v2.5
- Different global Ingest endpoints. OIS v2.5 uses the following ingestion endpoints: Main (transfer.ooyala.com), US (transfer-us.ooyala.com), EU (transfer.ooyala-eu.com), and APAC (transfer-apac.ooyala.com). The main endpoint automatically redirects users to the closest region. You can also access region-specific endpoints directly.
- Upload-only user accounts. In the Backlot GUI (Account > User Management), you can now add a user with Upload Only permissions to your account (see Managing Users). You can then use the email and password associated with this user to log into the new ingestion endpoint at transfer.ooyala.com when using either an FTP or Aspera client.
- Expedited enablement for manifest-based ingestion. The process of enabling manifest-based ingestion has been streamlined, resulting in a faster turnaround for enablement requests. Your request automatically includes support for both XML and CSV manifests (you no longer request just one or the other).
- Ingesting via FTP or Aspera. By creating upload-only users, you no longer need to contact Ooyala to get special credentials for FTP or Aspera. Files are now deleted right after they are processed. Submitted files that do not go through the entire ingestion workflow (for example, awaiting the upload of a manifest) are deleted from the server after 7 days.
- Updating remote assets using MRSS. You can now update remote assets in Backlot using MRSS feeds with new metadata, thumbnails, and closed caption files.
- Creating remote assets using CSV You can now create remote assets using CSV ingestion. This adds a third option to existing support for remote asset creation using XML and MRSS ingestion.
- Non-conforming workflows. For OIS 2.5, manifest-based ingestion workflows must conform with Ooyala’s DTD standard. Backlot rejects non-conforming workflows but does not yet notify the user of the validation error.
- Ingest validation. The OIS v1 use of md5 hash algorithms to validate ingested files is not yet available in OIS v2.5.
- Integrating Third-Party Players with IQ Using the JSON API: Added new documentation about the Ooyala IQ JSON API.
- Ooyala IQ SDK for Roku Integration: Added new documentation about how to implement the Ooyala IQ SDK for Roku integration.
- Ooyala IQ Roku Library API Documentation: Added new API documentation (including a tutorial) for the Ooyala IQ Roku Library.