Patent US20090018898 - Method or apparatus for purchasing one or more media based on a recommendation - Google Patents. This application claims the benefit of U.S.
Provisional Application No. 60/937,776, filed on Jun. 29, 2007, and of U.S. Provisional Application No. 61/000,592, filed on Oct. 26, 2007. The entire teachings of the above applications are incorporated herein by reference. Music is often embedded in a variety of videos including commercials, television shows, movies aired on television (TV), Digital Video Discs (DVDs), and streaming video on computer networks, such as the Internet. At present, individuals watching videos have no way to quickly and easily identify the artist who created a particular song being played during the presentation of a given video, much less purchase a copy of the song in question. Unfortunately, many commercials, television shows, movies, and streaming videos feature abbreviated versions of songs, which are difficult to identify.
The present invention provides a solution to the problems of the prior art. A description of example embodiments of the invention follows. Echonest/echoprint-ios-sample - GitHub. API – Last.fm. API. Overview This document describes the TuneFind REST API.
The API provides methods for reading most of the data found on TuneFind.com. All API requests are secured, authenticated, and rate-limited as described below. Use of our data is subject to the TuneFind Terms of Use and TuneFind API Terms of Use. Per these terms Standard API users must not cache or store API data in any form for longer than than 24 hours. There are two versions of the TuneFind API, Standard and Premium. The TuneFind Premium API is a paid service. The TuneFind Standard API is a free service. Endpoint and Versioning The TuneFind API is offered via HTTPS only. We may add fields, add methods, and fix API bugs without incrementing the version number. Authentication All API requests must be authenticated via HTTP Basic Authentication.
Curl -u user:pass Encoding All responses are provided in the UTF-8 character set and default to JSON encoding. Requests may be made in either HTTP/1.0 or HTTP/1.1. Data Types Rate Limiting Caching. Rovi Cloud Services - @ developers.seevl.net. Song API Methods — The Echo Nest v4.2 documentation. You can call song/identify with GET or POST.
Identifying songs with POST Posting tracks with /song/identify can be done in two manners An HTTP POST request with Content-Type "multipart/form-data" where all parameters are in the post body and the query is in the "query" parameter of the post "files"An HTTP POST request with Content-Type "application/octet-stream", with the local query file as the body of the request, and the parameters in the URL Example POSTs: Identifying songs with GET If you call song/identify with GET, you give the code parameter directly along with any metadata fields: Here is a sample query: The query parameter needs to be a JSON dictionary and can accept the following fields: metadata: a JSON dictionary containing 0 or more of the following: artist, release, title, genre, seconds, filename, version.
Code: required. Any additional keys in the query are ignored. Here is an example response: