I'm working on a project that collects music data from various sources like Spotify and Tidal, using identifiers like ISRC or track ID. My current database has about 350 million tracks, and I've implemented some useful endpoints:
1. **/audio-features** - provides data about the track's characteristics.
2. **/track** - delivers detailed info about a specific track, including its title, artist, album, and more.
3. **/platforms** - lists where a track can be streamed across different platforms, alongside links.
I also have endpoints for playlists (public only) and albums, but I'm not sure what additional features would make my API more comprehensive. Any suggestions?
3 Answers
Honestly, this sounds pretty useless. It's hard to see the value in it.
I think enriching your API with artist-level and album-level data would be a smart move. Consider adding genres, record labels, release types, explicit content flags, and preview URLs. A feature that tracks changes in IDs across platforms could enhance usability, making it more appealing for real-world applications.
I already have those. I'm just focusing more on the audio features since I've invested a lot of time into that.
This API could really benefit from including lyrics, especially if they're time-synced. You might also want to consider adding information about the license status of the tracks, a flag for explicit content, and even regional availability for each streaming platform. Chart positions could be useful too, although that might require extra work to keep updated.
Sure!
For you, maybe? People actually pay for this data, and I’m looking to make it available for free.