API and data

ListenDex uses official music data sources and caches aggressively.

This page documents the data-source posture needed before ads, subscriptions, public widgets, or broader API access. It is not a public developer API contract yet.

Spotify

Metadata source

Used for: Catalog search, album/track metadata, artwork, Spotify OAuth, recently played import, and user-uploaded Spotify export matching.

Readiness requirement: Use official API flows, follow developer policy and design guidelines, show required attribution/branding where Spotify data or artwork appears, and do not scrape.

Last.fm

Metadata source

Used for: Artist info, similar artists/albums, cover art fallback, top tracks, and scrobble import by username.

Readiness requirement: Keep ads and paid reports off Last.fm-heavy pages for conservative launch. Contact Last.fm before expanding commercial use that materially relies on Last.fm data.

MusicBrainz

Metadata source

Used for: Open music metadata and release group identifiers.

Readiness requirement: Respect MusicBrainz rate limits, attribution expectations, and data license requirements.

Cover Art Archive

Metadata source

Used for: Cover artwork fallback by MusicBrainz release group identifier.

Readiness requirement: Use official archive URLs and preserve source awareness for takedown or artwork disputes.

Public integration roadmap

RSS feeds are available at profile RSS URLs for public reviews and lists.
Embeddable widgets should start with profile badges, recent reviews, lists, album ratings, and year-in-music cards.
Any public API must document authentication, rate limits, attribution, acceptable use, caching, and removal requests before launch.