Audioburst Personalized Playlist

Overview

This document provides instructions on how to get and manage user’s personalized playlists.

Audioburst personalized playlists provide listening identities that follow your users’ habits and desires. Audioburst’s AI-based audio engine organizes audio content every day. Our platform listens to, understands, segments and indexes millions of minutes of audio information from top radio stations and podcasts. From the Audioburst segmentation process, we can create personalized listening identities, an experience now available to all developers through the following set of APIs:

Instructions

POST Register User - Use this API to create a UserID for each of your users, POST this ID to Audioburst.
GET User Preferences - Use the personalized API to get the listening identity preferences. Display the preferences on your application’s user interface to allow your users the ability to set their preferred news categories and topics. Audioburst listening identities are built from trending news topics, as well as other themed categories and subcategories, such as sports and entertainment.
(You can review all supported topics using the GET User Preferences API.)
POST Set User Preferences - After the user has selected their desired topics from the UI, post the user’s preferences to Audioburst. Preferences will be set for the user’s listening identity and will be kept until you POST new preferences.
GET Personalized Playlist API - Each time the user asks for the personalized playlist, use the GET personalized playlist API following the UserID.
Display Audioburst personalized configurations - Provide your users with the option to configure their listening identity on a usable user interface. This interface could be accessible from your app side menu, a personalized screen or any other location that will be accessible to the user.
(See our UX recommendations below for ideas on developing an appropriate user interface.)
To display your user's configurations above the complete list of Audioburst topics, use the GET Personalized Playlist API call along with the GET User Preferences API call. On the UI mark, the user selected categories and topics will be previewed above the Audioburst topics. If the user made any changes to their listening identity, use the POST Set User Preferences API with the UserID to send the new configuration to Audioburst.

UX recommendations

Personalized onboarding:

Open the personalized playlist for the first time. (Screen 1)
The user selects categories or topics to be included in the playlist. (Screens 2,3)

Add user generated topics:

Select the option to add a topic. (Screen 1)
The user inputs a topic into the playlist. (Screen 2)
The user can remove the topic by tapping the ‘x’ next to its listing. (Screen 3)

Provide a UI to change the user personalized playlist configuration:

Set a place to configure the personalized playlist. (Screen 1, 2)
The user can tap selected topics to unselect, or delete their customized topics by tapping the ‘x’ next to its listing.

"Audioburst API"	means the Audioburst application programming interface to be used on your online services and mobile applications as described in the Documentation.
"Audioburst Marks"	means the Audioburst name, marks and logos and all other proprietary identifiers used by Audioburst in connection with the Services, and all trademarks and/or trade names of Audioburst, whether registered or not.
"Confidential Information"	means any and all information and data, in whatever form, including whether disclosed orally or in writing, including but not limited to any and all patent and patent applications, trade secrets, proprietary and confidential information, ideas, samples, techniques, methods, technology, works of authorship, models, inventions, know-how, processes, equipment, prices, customer and partner information related to the past, current and future products and services, including information concerning research, development, financial matters, procurement, manufacturing, investors, employees, business relationships, forecasts, sales and marketing plans and any improvements and enhancements thereof; information available in premises of a Party entered by the other Party or representatives thereof; and information received from others that the disclosing Party is obligated to treat as confidential.
"Documentation"	means all written documents provided or made accessible by Audioburst to you on https://developers.audioburst.com, containing the instructions for implementation of the Audioburst API in connection with the Services under these Terms.
"End User"	means those individuals end users who have access to use your Product which contains Audioburst's API in the Territory.
"Monetization Owner"	means either one of us owning and controlling the monetization for generating Revenues from, the promotion of the output provided by the API within your Product from either monetization platform including (i) ad server, (ii) ad agency, (iii) advertiser, (iv) End User (the "Monetization Platform") or any of us paying for generating revenues from your Product containing Audioburst API.
"Net Revenue(s)"	means the gross revenues actually received by the Monetization Owner from the promotion of the output provided by the API, using the Audioburst API within your Products, less duties, distribution costs and third party revenue share, advertisement costs, insurance, duties, discounts, adjustments, deferrals, rebates, sales commissions and incentives, third party license fees, taxes, and similar charges incurred by the Monetization Owner, if any, with respect to such promotion of any output provided by the API.
"Revenue Share"	means if Audioburst is the Monetization Owner - 25% from the Net Revenues and if you are the Monetization Owner – 50% from the Net Revenues.
"Territory"	means Worldwide.