Spotify Audio Features API Alternative: What Actually Works in 2026

Updated September 9, 2026. Correction: an earlier version incorrectly said Spotify required 250,000 monthly active users for Development Mode. That requirement applies to extended quota partner eligibility.

If your Spotify app cannot access Audio Features, there are other ways to get BPM, key and related measurements. The choice depends on whether you have audio files to analyze or need to look up an existing recording.

Spotify restricted Audio Features and Audio Analysis access for new Web API use cases in November 2024. Access depends on the app's eligibility; saying the endpoints disappeared for everyone would be inaccurate.

Spotify's Development Mode requires the app owner to have Premium and limits an app to five authorized users. The 250,000 monthly active user requirement belongs to extended quota partner eligibility. Check Spotify's current rules when evaluating an integration.

The Landscape Right Now

There are really only a few categories of solutions:

1. Self-Host an Analysis Pipeline

You can run Essentia or librosa yourself. These are legitimate open-source audio analysis libraries that can extract BPM, key, energy, and other features from audio files.

You need audio you are permitted to process, plus a way to run and maintain the analysis. Setup effort depends on the scope of your application.

A local library can also fit a small project when you already have the audio and can handle the processing.

2. Evaluate Hosted APIs

Check the source of the measurements, field coverage, rate limits and billing rules. Similar field names do not establish that two services produce equivalent values. A Spotify-shaped response alone does not tell you where its data came from.

MeloData is one option. I built it. Here is how it handles lookups, what it costs and where its data falls short.

How MeloData Works

MeloData is a REST API that looks up available audio features by ISRC (International Standard Recording Code). The data comes from two sources:

AcousticBrainz Archive. Before it shut down in 2022, the AcousticBrainz project analyzed millions of tracks using Essentia and released the data publicly. We imported a 50K-track curated subset (mapped to ISRCs via MusicBrainz) as our seed dataset, and can attempt live analysis when a suitable audio preview is available.

On-Demand Analysis. For tracks not in the archive, we run our own Essentia-based analysis pipeline. You get a 202 response (meaning "we're working on it"), and the response asks you to retry after 30 seconds. That is a polling interval, not a completion guarantee. Completed results are cached for later requests.

The live analysis runs on audio previews using open-source tools. Archive and live results have different field coverage.

What You Get Back

GET /api/v1/tracks/USRC17607839/features

The response contains a data object with the recording's metadata and available features. Completed records also report source and analysis_version. Check the response state before reading features: an uncached request can return HTTP 202, and a later response may be partial or unavailable.

If you have a title and artist instead of an ISRC, use the name resolver first and check the matched recording. There's also search, batch lookups (up to 50 tracks), artist data, metadata, and a recommendations endpoint.

What About Spotify's Response Format?

One thing to be aware of: MeloData does not mirror Spotify's exact response format. Spotify's audio-features endpoint returned things like track_href, uri, and type fields that are Spotify-specific.

If you're migrating from Spotify's API, you'll need to map some field names. Fields with similar names can use different methods. BPM is a tempo, key is a label, and live loudness attempts LUFS with an RMS-derived dB fallback. The response does not label that fallback separately. Some scores use a 0 to 1 range, but that does not make them interchangeable with Spotify scores. Several fields can be null.

Pricing

Current direct plans include 1,000 monthly lookups free, or 25,000 for $19 per month on Dev. Additional lookups cost $0.002 each when overage billing is enabled. That overage rate is separate from the included allowance.

For the ordinary feature endpoint, HTTP 200 and 201 responses count toward usage. HTTP 202, 429 and 5xx responses do not. A successful partial or unavailable response can still count, so billing does not promise a complete feature set. Batch and saved bulk jobs have their own accounting rules in the documentation.

What MeloData Doesn't Do

No Spotify login integration. You can't use this to access a user's Spotify library. We provide audio features for tracks, not Spotify account data.
No lyrics. MeloData does not provide lyrics.
Coverage isn't 100%. We have 50K+ pre-analyzed tracks from the AcousticBrainz archive plus live analysis where a suitable preview is available, but obscure tracks might not have Deezer/iTunes audio previews available for analysis. When no preview is available, a lookup can return partial metadata or an unavailable result.
Preview-window analysis. Live analysis runs on 30-second audio previews, not full tracks. Tempo, key and time signature can vary within a recording, and detection can be wrong. Loudness and energy reflect the preview window. For songs with wide dynamic range, those values can differ from the full master. See the Data Sources & Limitations page for the full breakdown.
Not a real-time streaming integration. This is a lookup API, not a playback API.

How to Evaluate Any Alternative

If you're comparing options, here's what I'd look at:

Where does the data actually come from? Check whether the provider has the access and permissions its workflow needs.
What happens when a track isn't in the database? Some APIs just return 404. MeloData can queue analysis and return a retry interval; it cannot guarantee that audio or a complete result will become available.
What's the actual per-request cost at your volume? Some APIs have cheap base plans but expensive overage.
Is there a free tier for development? You shouldn't have to pay to prototype.
Can you test it right now? MeloData's docs include request examples. No signup is required to read them.

Getting Started

curl https://melodata.voltenworks.com/api/v1/tracks/USRC17607839/features \
  -H "Authorization: Bearer YOUR_API_KEY"

Free tier: 1,000 lookups/month, no credit card.

For the implementation details, read why I built MeloData.

Access rules above were checked against Spotify's own documentation on September 9, 2026.