Jamendo API Introduction
Welcome to the Jamendo API documentation!
Please use our Api to build awesome music applications, support independent artists and express your creativity through mash-ups and innovative products!
We provide more than 20 different read methods to access a catalog of half-a-million tracks, some powerful features for music discovery like search and radios, OAuth2 based authentication, 5 write methods to manage user library, and a website to monitor your app statistics.
Developer.jamendo.com will help you discover the various features available through our API and will give you thorough explanations about how to implement them in your application. Have a great time using our API and don't hesitate to share the outcome of your work with us!
Every Jamendo Api method is generically expressed as an entity or entity+subentity. The generic GET url form is the following:
As some of the RESTfull specifications (like the CRUD actions 1-1 mapping through HTTP methods, or the entity Id received as get parameter) are not implemented in our framework, we prefer to define our API as RESTlike.
Read methods need an http or https GET method, while write methods need a POST. Note that you can and definitely should always use SSL to improve your application security, and you must use it in certain parts of the OAuth process.
Every Api call returns a response document in the requested format: json, jsonpretty, xml. Such a response document (with a slightly different structure depending on the used format), will always contain some headers, and the results requested by your Api call.
On every read method's documentation page and write method's documentation page you can see an example of a request and the corresponding response document.
If you have any questions, suggestions, bugs or malfunctions to report, write us and actively participate to the Jamendo GoogleGroup! Someone from our team or from the developer community itself will answer you as soon as possible.