Music · head-to-head

Deezer vs Lyrics.ovh

Deezer

Deezer's REST API serves the catalog metadata behind the streaming app: tracks, albums, artists, playlists, charts, and full-text search. Unusually for a major streaming service its read endpoints are fully keyless — a plain GET against api.deezer.com returns real track data with no App ID, key, or token at all — while OAuth is reserved for endpoints that act on a user's own account, such as favorites or the activity feed. Responses can be requested as either JSON or XML via an output query parameter, and the API is free to use within Deezer's terms.

Lyrics.ovh

Lyrics.ovh is a small keyless lookup service: GET a artist/title pair against api.lyrics.ovh/v1 and it fans that query out in parallel across sources like Genius, AZLyrics, and Letras.mus.br, returning the first full lyric text found as plain JSON. There's no authentication, no request quota, and no dashboard — it's a single open-source Node project (github.com/NTag/lyrics.ovh) that anyone can also self-host. The stored Apiary docs mirror has gone dead (502), but the live API itself responded with real lyrics during this check and sends a wildcard CORS header.

DeezerLyrics.ovh
AuthenticationNoneNone
Pricingfreefree
FormatsJSON, XMLJSON
CORSnoyes
HTTPSYesYes

Lyrics.ovh supports CORS, while Deezer doesn't — pick Lyrics.ovh for direct browser calls.

More comparisons