We’ve all been there. We found a great song we love, but don’t know the lyrics. Instinctively, you hit the Google search and wade through a sea of misspelled, poorly translated, out-of-date, or poorly interpretted lyrics listings. Granted, some songs come tagged with the lyrics, which is helpful, but that’s not going to help the rest of your massive music collection of songs you’ve been singing along to. It’s frustrating and it’s messy, something the MusixMatch API could change.
Doing lyric search well has value, which is why MusiXMatch has a great write-up in Forbes. MusixMatch aims to be the premiere source of authorized, organized, and verified lyric information. It could also be music to developer ears, as we wrote last February.
What MusixMatch Does
Before we get into the API itself, it’s important to understand what MusixMatch is actually offering. At its core, MusixMatch is a database of authorized and authenticated lyrics. The major point here is that the lyrics are authenticated and authorized from proper sources, rather than submitted by users who may or may not know what the lyrics actually are. Reading through comments on lyrics sites will instantly show you how valuable this is. No debating lyrics, which alter what the song means entirely. Additionally, you are also given detailed data on who performed a song, related songs, genres, and even influences, for starters. As you dive in to the API, you’ll quickly find that MusixMatch is what you want, driving your music applications for lyric metadata.
As if organizing and gathering this information wasn’t enough, MusixMatch is primarily an API. Meaning it was built from the ground up to handle being in your application. Like all great APIs, this is pretty RESTful and straightforward. You make calls against the API endpoints and get data back in JSON, XML, or JSONP format. That’s all there is to it. Currently, there’s no authentication system to go through, but you are limited to 2000 hits (calls) per day, so try to b frugal. I suspect much of this data isn’t very volatile, so caching is probably not a bad idea (I didn’t see anything in the API TOS that forbid caching, but as always, do the research before you do this).
Now… if someone could mash this up with the Rdio API and a lyric-stripping audio processor, we can have the ultimate karoake machine.