sv443 / geniurl

REST API that searches for song metadata, including the lyrics URL, translations and more from genius.com - supports JSON and XML

Hi there, I'm Sven

I am a 22 year old full stack developer from Germany.
My interests are in open source software, server and web development, as well as PC and server hardware and IT infrastructure.
Most of my projects are made with or for Javascript, Linux and Arduino.
Although I love working in a familiar environment, I'm always open to try out new technologies and want to continue learning and improving my skills.

What I'm currently working on:

• JokeAPI is an API that serves a good variety of uniformly formatted jokes and offers lots of filtering methods.
• BetterYTM, a userscript that brings tons of features and UX improvements to YouTube Music.
• geniURL, an API for looking up and filtering song metadata from genius.com
• Userscript.ts, a Template for making Userscripts in TypeScript with tons of modern utilities and comfort features.
• SvCoreLib, which is a Node.js package that is used in basically all of my JavaScript projects. It contains many miscellaneous features.

---

My projects are free and open source so I rely on donations to keep my servers and domains running.
So if you like what I do, please consider supporting my development.

If you want to reach out to me, you can join my Discord server or send me an E-Mail.
_{Please don't contact me with any job offers or shady business requests, you will be ignored.}

---

Links: Homepage • npm

geniurl's Issues

Add better result filtering

Through something like fuse.js

Fix fuzzy filtering

• Exact matches of song / artist or the entire query should be preferred over all other results.
• When the query includes parentheses (ft. xy), (xy Remix), they should be considered while doing the exact matching.
• Score distribution is unreliable and too "loose"

Examples:

• https://api.sv443.net/geniurl/search?artist=Skrillex&song=Summit
• https://api.sv443.net/geniurl/search?artist=Petit%20Biscuit&song=Problems
• https://api.sv443.net/geniurl/search?artist=Upsahl&song=Drugs

Add info about the associated album(s)

Fix inconsistent unicode characters before fuzzy filtering

Example: /search?artist=Apashe&song=I'm Fine
The correct result (ranked at 2) contains a weird unicode apostrophe: ’ instead of the regular one: '
This throws off the fuzzy filtering.
The prop normalization for title, fullTitle, and artists should include this "character remapping"

Invisible characters in genius API response

like seriously, why

Support fuzzy search for the `?q` param

idk if this is possible or reliable but I should look into it

Migrate from postman to a different service

• https://hoppscotch.io/
• https://insomnia.rest/
• https://httpie.io/
• https://www.httpiness.com/

Add unit tests

Deal with genius API hiding song language behind second API call

For some reason the song language has been removed from /search?q and is now only available in /songs/$id
This has broken the ?preferLang param.
Possible solutions:

• Offer extra endpoints for "simple" info and "advanced" info, with different rate limits (and latencies, oof)
• Always make a second API call at the cost of latency (yuck eww disgusting)
• idfk

Fix errored response for /translations

Every time the error property is true, a message property should be present and the translations property should not.
Also it is unclear whether the song ID is invalid or there just aren't any translations.

Add route `/translations/:id` to get song translations

This would use the endpoint at api.genius.com/songs/:id to filter and return the items in response.song.translation_songs.

Use MediaMetadata API for reading song title and artist

MDN Reference

Make fuzzy search threshold configurable

?threshold would be a URL param that takes a float between 0.0 and 1.0 to change from the default fuzzy search threshold of 0.6

Add param `?preferLang=xy` to prefer results of a specific language in fuzzy filtering

Sometimes translations of a song will be considered more relevant by the genius API (and they have the exact same type and structure as the original lyrics) so this could be an additional way to improve result ranking.
This could make use of #11, by checking each items' language prop.