Difference between revisions of "MusicBrainz API"

From MusicBrainz Wiki
(Created page with "The MusicBrainz API can be accessed in two formats, XML and JSON. See below for a general FAQ, and see the documentation pages for the XML API and the JSON API for mo...")
 
Line 1: Line 1:
 
The MusicBrainz API can be accessed in two formats, XML and JSON.
 
The MusicBrainz API can be accessed in two formats, XML and JSON.
  
See below for a general FAQ, and see the documentation pages for the [[XML API]] and the [[JSON API]] for more details on how to use each version.  
+
See below for a general FAQ, and see the documentation pages for the [[MusicBrainz API/XML|XML API]] and the [[MusicBrainz API/JSON|JSON API]] for more details on how to use each version.  
  
 
== General FAQ ==
 
== General FAQ ==
 
{{:Development/WS_FAQ}}
 
{{:Development/WS_FAQ}}

Revision as of 15:01, 7 July 2020

The MusicBrainz API can be accessed in two formats, XML and JSON.

See below for a general FAQ, and see the documentation pages for the XML API and the JSON API for more details on how to use each version.

General FAQ

What can I do with the MusicBrainz API?
You can look up information about a particular MusicBrainz entity ("give me info about The Beatles"), browse the data to find entities connected to a particular entity ("show me all releases by The Beatles"), or search for entities matching a specific query ("show me all artists matching the query 'Beatles' so I can find the one I want and ask for more data").
Who can use the MusicBrainz API? Is it free?
Non-commercial use of this web service is free; please see our commercial plans or contact us if you would like to use this service commercially.
Do I need an API key?
Currently, no. But you must have a meaningful user-agent string.
Do I need to provide authentication?
Data submission, as well as requests that involve user information, require digest authentication.
Which formats can I get the data in?
The API was originally written to return XML, but nowadays it can also return JSON.
Is there any significant difference between the XML and JSON APIs?
For requesting data, the XML and JSON API are effectively equivalent. The XML API is the only one that allows submitting data to MusicBrainz (but keep in mind only ratings, tags, barcodes and ISRCs can be submitted via the API at all; for most data additions you should use the website instead).
Is there a limit to the number of requests I can make per second?
Yes. See our rate limiting rules.
This seems very complicated, can I see some examples?
Yes, we have an example page showcasing some queries and showing the returned format you can expect for each.
Are there language bindings for the API?
Yes, in many different languages. See our list of external libraries.
What should I do if I encounter unexpected behaviour not covered in these docs?
You can ask question in IRC or in the forums.
Check to see if a ticket has been filed in the bug tracker, and if not consider writing one.
What else should I know before I start using the API?
It'd probably be helpful to know:
So you're on version 2 of the API then? What happened to version 1?
The version 1 of the API was designed with the data structure of the original (pre-2011) version of the MusicBrainz database in mind. It was deprecated in 2011 when we changed to our current data schema, and after running (without further updates) for several years to avoid breaking any tools using it, it was finally taken down in 2019.