While the Popyoular API is designed to be simple and straightforward, please take the time to familiarize yourself with the following:
The basic concepts of the Popyoular API are lookup, collections and mapping.
The actual content delivered by the API, whether accumulated reviews in various forms or metadata, is provided by the lookup methods.
Which selection of content to return can be configured using collections. Collections allow you to group review sources, or just use all of them if you prefer.
Along the way, you can map your internal ID to the Popyoular identifier. Mappings can be stored by the Popyoular API, removing the need for you to build functionality for this on your side.
The benefits of mapping your entire catalog are substantial: Most importantly, we can deliver various types of top lists that are already tailored to the actual contents of your service without the need for you to do anything. Another benefit is that whenever you use the lookup methods, you can simply use your own internal ID to get the correct data.
While matching and lookup can be done just-in-time, we recommend the separate approach described above.
The Popyoular URL-structure is designed to be short, efficient and as human-readable as possible. The core concept is to use URLs as unique identifiers. Thus, what’s easily readable for anyone in a browser address bar is identical to what’s used under the hood.
Conflicts over URLs are solved by adding a number, such as “…/the-wall-1″
Please use the floater to navigate the API-description, or continue to release lookup.
Popyoular currently supports reviews for music and movies. The movie and music API are very similar and unless otherwise stated the calls are identical (apart from the URL prefix). Also, whenever the subject (movie or album) is returned as a part of the response, it will contain a <movie> or <album> tag respectively.
The Popyoular API supports two methods of authentication & authorization