Brand Brand
  • API docs(current)
  • Jamendo Apps
  • Jamendo-Dev GoogleGroup
  • Your account
  • Introduction

    • Rest-like API
    • Http[s] methods
    • Document format
    • Old (deprecated) Api
    • XML dump
    • Need an help?
    • Api Terms of Use
  • Authentication

    • App authentication
    • Oauth2 introduction
    • Workflow
    • Requirements
    • Wich API methods
    • OAuth2 Authorize request
    • OAuth2 Grant request (new)
    • OAuth2 Grant request (refresh)
  • Response Codes

  • Read Methods

    • albums
      • file
      • tracks
      • musicinfo
    • artists
      • tracks
      • albums
      • locations
      • musicinfo
    • autocomplete
    • feeds
    • playlists
      • file
      • tracks
    • radios
      • stream
    • reviews
      • albums
      • tracks
    • tracks
      • file
      • similar
    • users
      • artists
      • albums
      • tracks
  • Write Methods

    • setuser
      • fan
      • favorite
      • like
      • dislike
      • myalbum

Jamendo Api Response Codes

Every call returns a document containing headers and results. The headers are composed of four fields:

  • status: it can be either 'succeed' or 'failed'
  • code: will be 0 in case of a success or an error Id (different then zero) in case of a fail. All the information you need is in the table below.
  • error_message: contains the error message if an error occured else it is empty. Every error message will contain the type of the error (see in table below) as well as the contextual error description
  • warnings: may contain warning messages if any. Warnings get raised, but do not let the request fail.


codetypedescription
0SuccessSuccess (or success with warning)
1ExceptionA generic not well identificated error occurred
2Http MethodThe received http method is not supported for this method
3TypeOne of the received parameters has a value not respecting requirements such as type, range, format, etc
4Required ParameterA required parameter was not been received, or it was empty
5Invalid Client IdThe client Id received does not exists or cannot be validated
6Rate Limit ExceededThis requester app or the requester IP have exceeded the permitted rate limit
7Method Not FoundJamendo Api rest-like reading methods are in the format api.jamendo.com/version/entity/subentity (subentity is optional). This exception is raised when entity and/or subentity methods don't exist
8Needed ParameterA parameter needed because of an imposed local condition was not received or/and has not the needed value
9FormatThis exception is raised when the api call requests an unkown output format
10Entry PointThe used IP and/or port is not recognized as valid entry point
11Suspended ApplicationThe client application has been suspended (illegal usage, ...)
12Access TokenInvalid Access Token.
13Insufficient ScopeInsufficient scope. The request requires higher privileges than provided by the access token
21Invalid UserSome parameters of User is not valid.
22Email Already ExistThe email is already used by another user.
23Duplicate ValueThis error is raised when a client tries to write or update a value which already exists and cannot be duplicated
24Invalid PlaylistCheck your playlist id.
101Access CodePlease check if you have correctly typed in your access code and if your subscription is still marked as being active in your client space.
API powered by 3scale API Management solution
  • Contact
  • Jobs
  • Api Terms of Use
Jamendo Music logo Jamendo Licensing logo