Maybe you run a gym, a café, a fitness app or a music community, and you want your customers to find songs, save them, and get playlists built for them without leaving your product. That is a lot to build from scratch. TIDAL offers it through an API, which is a way for your software, or an AI assistant working on your behalf, to ask TIDAL for music information and act on a listener’s library.
An API is a set of doors into a service that other software can knock on. Your app sends a request, like “find this song” or “add this track to my playlist,” and TIDAL sends an answer back. No copying and pasting between apps.
What TIDAL does
TIDAL is a high-fidelity music streaming service owned by Block. Its developer platform covers catalog details about albums, artists and tracks, personalized recommendations, playlists, a listener’s saved collection, search and more. One thing to know up front: TIDAL says the actual audio playback is limited to its official Player SDK for web, iOS and Android, so the API is about everything around the music, while the SDK plays it. You can find them at tidal.com.
What you can get done
Manage a listener’s music library
Audio & Music is the everyday work of a music service: the tracks someone saved, their playlists, their mixes. With TIDAL your product can read and change what a listener has collected.
GET /userCollectionTrackslists the tracks a listener has saved.POST /userCollectionTracks/{id}/relationships/itemsadds tracks to that saved collection.DELETE /userCollectionTracks/{id}/relationships/itemsremoves tracks from it.GET /userCollections/{id}reads a listener’s whole collection.
Look up albums, tracks and artists
Metadata Cataloguing means the descriptive details that make music findable: titles, artists, credits, genres. This is how you show a proper album page or track listing inside your own product.
GET /albumsretrieves a set of albums.GET /albums/{id}retrieves one album.GET /albums/{id}/relationships/albumStatisticsgets statistics for an album.GET /tracksretrieves a set of tracks.
Serve up personal recommendations
Content Recommendation Modelling is the “you might also like” part. TIDAL builds mixes for each listener, and your product can fetch them.
GET /userRecommendations/{id}gets a listener’s recommendations.GET /userRecommendations/{id}/relationships/discoveryMixesgets their discovery mixes, music they have not heard yet.GET /userRecommendations/{id}/relationships/myMixesgets mixes built from what they already like.GET /userRecommendations/{id}/relationships/newArrivalMixesgets mixes of new releases.
Workflows that put it together
A workflow is a recipe: several calls made in a set order to finish one job. We publish these for TIDAL as Arazzo workflows on APIs.io.
- Search and Save Track to Collection searches for a track, confirms it, then adds it to the listener’s collection.
- Create Playlist and Add Tracks creates a new playlist, then adds a track to it.
- Artist Discography Explorer finds an artist, then walks their albums, top tracks and similar artists.
- Discovery Mix Tracks reads a listener’s discovery mix and resolves the tracks in it.
- Album Tracklist Explorer reads an album and works out its tracks and artist.
- Track Playback Manifest finds a track by its ISRC, the standard recording code, and fetches what a player needs to play it.
Getting started
TIDAL is freemium with self-serve signup, and it is a hosted service, so you call their endpoint rather than running anything yourself. Cost details live in the Pricing section of the TIDAL profile. TIDAL’s documentation includes an API and SDK overview, the API reference and a walkthrough of its recommendation APIs.
On APIs.io you can browse the full TIDAL profile and APIs such as the Playlists API, the Albums API and the Artists API.
Start with search and save: let your customers find a song and keep it, and build the rest of the experience from there.
