Welcome to TheAudioDB API, your ultimate destination for seamless access to free, real-time Music data.
Whether you're building an app, running a music site, or simply want to stay updated with Artists, Albums, Songs,
or Music Venues, our powerful and easy-to-use API has you covered.
With support for a wide range of Music and labels worldwide, TheAudioDB API is designed for developers, enthusiasts,
and startups looking to integrate reliable Music data without the hassle of expensive subscriptions.
Get started today and bring the game to life in your application!
Free vs Premium
We offer a free API that anyone can use. The site originally had all methods available to use under the free API with no limits,
but sadly it became too popular and was abused.
So over the years we have had to limit certain methods, while trying to keep the core functionality.
The Free API should work in many use cases, so please do test it out.
The current free API key is: 123
Premium API keys can be found on your user profile, once upgraded.
The Premium API includes all methods in V1 with larger limits as well as some extra stuff like livescores and video highlight links.
Premium also allows you to use the more modern V2 API. You can find your Premium API key on your user profile if you are a supporter.
API v1 vs v2
The v1 API was written over 10 years ago and has been addded to since with many extra features.
It uses basic PHP code to produce JSON objects that are returned to the user.
API users are authenticated with a simple numeric API key in the URL.
The naming is a little messy and the authentication is not great, as the key is visible to anyone who wants to poke around your web requests.
Saying that, it works and is simple to use and easy to test in any web browser. Ideal for beginners!
V2 API is more modern and verbous API.
This means it should be easier to understand in a logical way.
It also uses more modern authentication requiring the API key to be sent in the header.
When something goes wrong, the API will return standard HTTP response codes.
V2 is only for premium subscribers and will be the only version developed going forward.
Base URL
The Base URL is a crucial element for making API calls, enabling you to clearly specify the root URL(s) for API requests.
When making API calls, you combine the base URL with the specific endpoint path to form the complete request URL.
v1 Base URL = https://www.theaudiodb.com/api/v1/json
v2 Base URL = https://www.theaudiodb.com/api/v2/json
V1 Authentication
v1 of the API has a very simple authentication process.
Simply use the base URL above and append the number /123/ to the URL for the test key or replace with your premium API key.
You can see an example below using a simple web browser using the free '2' API key:
V2 Authentication
v2 takes a more secure, modern approach to Authentication.
When sending a request to the API base URL, you must include API key in the header using this attribute 'X-API-KEY'.
You can see an example below using the popular free API testing software: Httpie
Images
Our site has a huge amount of images for things like events, players and teams. Most are fan created.
There are 2 types of images available. JPEG fanart and transparent PNG mostly used for badges and logos.
You can see the different types of artwork and sizes on this page.
You can access any image from the front-end using the image URL from the returned JSON data.
Preview Images
Most of the time you won't want to download the original large image, just get a small preview.
This is possible simple by appending '/medium', '/small', onto the end URL. This will give you a smaller version.
The site has different rate limits for different levels of users.
You will recieve a "429" http header if you breach the limit, then you will need to wait another minute until requests will work again.
We enforce these not just to differentiate our tiers, but to keep the overall performance of the site stable.
Free users 30 requests per minute. Premium 100 per minute Business 120 per minute
V1 API Documentation
v1 API Search
Most API requests will start with a string search. Examples of this may be to find a artist or song details.
All searches will return the entities data but also an ID number which can be used for later faster lookups.
Search Artist
Type:
Parameter:
Free Limit:
Premium Limit:
Example: JSON Data
Example 2: JSON Data
Example 3: JSON Data
Search for any Music team by its name. {strArtist} {Music_Brainz_Artist_ID}
Search Album:
Type:
Parameter:
Free Limit:
Parameter:
Free Limit:
Example: JSON Data
Description: Return single album details from Artist & Album name
Optional strings: {strArtist} {strAlbum}
Search Track:
Type:
Parameter:
Free Limit:
Parameter:
Premium Limit:
Example: JSON Data
Description: Search for any Music person by their main or alternate name. {strArtist} {strTrack}
While the string search is useful above to find things, it is actually much quicker and simpler to retrieve data using the unique ID.
Lookups will return all data from that entity, you can find any ID by simply looking at the frontend websites URL usually.
For example the Coldplays ID is 111239, or the Deftones is 112573.
Lookup Artist:
Type:
Parameter:
Free Limit:
Premium Limit:
Example: JSON Data
Example 2: JSON Data
Example 3: JSON Data
Lookup a Artist details using its ID {albumid} or {Music_Brainz_Artist_ID}
Lookup Album:
Type:
Parameter:
Parameter:
Free Limit:
Premium Limit:
Example: JSON Data
Example 2: JSON Data
Example 3: JSON Data
Lookup Album details using its ID {artistid} {albumid} or {Music_Brainz_Release_Group_ID}
Lookup Track:
Type:
Parameter:
Parameter:
Parameter:
Free Limit:
Premium Limit:
Example: JSON Data
Example 2: JSON Data
Example 3: JSON Data
Lookup Track details using its ID {albumid} {trackid} or {{Music_Brainz_Recording_ID}
Using the list API means we can return more than one record.
This can be useful for example to list Music or countries
Music Videos:
Type:
Parameter:
Free Limit:
Premium Limit:
Example: JSON Data
Example 2: JSON Data
List all the music videos for an artist ID {artistid} {MusicBraind_Artist_ID}
Music Charts:
Type:
Parameter:
Free Limit:
Premium Limit:
Example: JSON Data
Example 2: JSON Data
Example 3: JSON Data
Example 4: JSON Data
List the top 10 songs for an artist by artist name {strArtist} or {Music_Brainz_Artist_ID}.
Search Artist
Type:
Limit:
Example: Live
Search for any Music Artist using a text string.
/api/v2/json/search/artist/coldplay
Search Album
Type:
Limit:
Example: Live
Search for any Music Album using a text string.
/api/v2/json/search/album/parachutes
Search Track
Type:
Limit:
Example: Live
Search for any Music Track using a text string.
/api/v2/json/search/track/yellow
v2 API Lookup
Lookup Artist
Type:
Limit:
Example: Live
Lookup full details for any artist using its unique ID {idArtist}.
/api/v2/json/lookup/artist/111239
Lookup Album
Type:
Limit:
Example: Live
Lookup full details for any album using its unique ID {idAlbum}.
/api/v2/json/lookup/album/2109615
Lookup Track
Type:
Limit:
Example: Live
Lookup full details for any track using its unique ID {idTrack}.
/api/v2/json/lookup/track/32724183
OpenAPI / Swagger
Introduction
The OpenAPI Specification (OAS) defines a standard,
language-agnostic interface to HTTP APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code,
documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a
minimal amount of implementation logic.
An OpenAPI Description can then be used by documentation generation tools to display the API,
code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases.
Postman Collection
Introduction
Postman is the single platform for designing, building, and scaling APIs—together.
Join over 40 million users who have consolidated their workflows and leveled up their API game—all in one powerful platform.
Artificial Inteligence MCP
Introduction
MCP (Model Context Protocol) is an open protocol that standardizes how applications provide context to LLMs.
Think of MCP like a USB-C port for AI applications.
Just as USB-C provides a standardized way to connect your devices to various peripherals and accessories,
MCP provides a standardized way to connect AI models to different data sources and tools.