MusicAPI vs Spotify API vs Last.fm API: Feature Comparison for Developers
Published on March 23, 2026
Building a music-powered application in 2026 means choosing from a growing landscape of music APIs, each with different strengths, trade-offs, and developer experiences. Whether you're building a playlist manager, a social listening app, or a recommendation engine, your choice of API will shape what's possible.
In this comparison, we put three popular options head to head: MusicAPI, the Spotify Web API, and the Last.fm API. We'll look at what each one offers, where they fall short, and which use cases they serve best.
Table of Contents
- Quick Comparison Table
- Platform and Data Coverage
- Authentication and Developer Experience
- Rate Limits and Quotas
- Pricing and Commercial Use
- Key Features Breakdown
- Which API Should You Choose?
- Frequently Asked Questions
Quick Comparison Table
| Feature | MusicAPI | Spotify Web API | Last.fm API |
|---|---|---|---|
| Supported Platforms | 12+ (Spotify, Apple Music, YouTube, Tidal, Deezer, SoundCloud, Amazon Music, and more) | Spotify only | Last.fm only (scrobbling data) |
| Unified Interface | Yes — single API for all platforms | No | No |
| Authentication | Single Sign-On with automatic token refresh | OAuth 2.0 per user | API key |
| Playlist Management | Full CRUD across all platforms | Full CRUD (Spotify only) | Read-only |
| Rate Limits | Based on plan (800–120,000+ requests/month) | Rolling 30-second window (undisclosed exact limit) | ~5 requests/second (unofficial) |
| Free Tier | Yes (20 users, 800 requests/month) | Yes (5 users in dev mode since Feb 2026) | Yes (non-commercial only) |
| Commercial Use | All paid plans | Free with Extended Quota approval | Requires separate commercial license |
| Real-Time Sync | Yes | Limited | No |
Platform and Data Coverage
MusicAPI: The Multi-Platform Connector
MusicAPI connects to 12+ music streaming services through a single, unified interface. Instead of writing separate integrations for Spotify, Apple Music, YouTube, Tidal, Deezer, SoundCloud, Amazon Music, Qobuz, Boomplay, Napster, Audiomack, and Audius, developers work with one standardized API.
This means your users can connect whichever streaming service they prefer, and your app handles them all identically. The data format is consistent regardless of the underlying platform — track metadata, playlist structures, and user libraries all follow the same schema.
Spotify Web API: Deep but Narrow
The Spotify Web API offers deep integration with the Spotify ecosystem. You get access to Spotify's rich catalog data, audio features, recommendations engine, and user library management. However, it only covers Spotify — if your users are on Apple Music or YouTube Music, you need a different solution.
Notably, Spotify made significant changes in February 2026, deprecating several endpoints including new album releases, artist top tracks, and bulk metadata requests. The Search endpoint's maximum results were also reduced from 50 to 10 items per request.
Last.fm API: Scrobbling and Metadata
Last.fm's API excels at one thing: listening history and music metadata. It provides scrobbling data, artist information, tag-based discovery, and listening statistics aggregated across its user base. However, it doesn't offer playlist management, streaming, or direct integration with other music services.
The API has a 100 MB data cap for reasonable usage, and accessing larger datasets requires written permission from Last.fm.
Authentication and Developer Experience
MusicAPI
MusicAPI provides a Single Sign-On system that handles OAuth flows for all 12+ supported platforms. Token refresh is automatic, so developers don't need to manage token lifecycle for each service individually. This dramatically simplifies the authentication layer of any multi-platform music application.
Spotify Web API
Spotify uses standard OAuth 2.0 with PKCE for user authorization. The developer experience is well-documented, but since February 2026, dev mode is limited to 5 test users and requires a Spotify Premium subscription. To serve more users, you need to apply for Extended Quota Mode, which involves a review process.
Last.fm API
Last.fm uses simple API key authentication for read operations and a session-based auth for write operations (like scrobbling). It's the simplest to get started with, but offers the least functionality of the three.
Rate Limits and Quotas
Rate limits can make or break your application's reliability. Here's how the three APIs compare:
| API | Rate Limit Model | Free Tier Limits | Scaling Options |
|---|---|---|---|
| MusicAPI | Monthly request quotas by plan | 800 requests/month, 20 users | Upgrade plan (up to 120K+/month), €0.40/1K overage |
| Spotify Web API | Rolling 30-second window | Undisclosed (dev mode: 5 users max) | Apply for Extended Quota Mode |
| Last.fm API | Per-second soft limit | ~5 req/sec, 100 MB data cap | Contact Last.fm for higher limits |
MusicAPI's approach is the most transparent — you know exactly how many requests you get per month at each pricing tier. Spotify intentionally keeps its exact rate limits undisclosed, which can make capacity planning challenging. Last.fm's limits are informal but enforced, and exceeding them can lead to account suspension.
Pricing and Commercial Use
MusicAPI Pricing
| Plan | Price | Monthly Users | Monthly Requests |
|---|---|---|---|
| Free | $0 | 20 | 800 |
| Starter | €189/month | 300 | 12,000 |
| Professional | €589/month | 1,000 | 40,000 |
| Business | €890/month | 3,000 | 120,000 |
| Enterprise | Custom | 3,000+ | Unlimited |
All paid plans include SSO for 12+ services, dashboard access, and support. A White Label add-on is available at €1,000/month for custom branding.
Spotify Web API
The Spotify Web API is technically free to use, but comes with significant limitations. Dev mode now caps you at 5 users and requires Premium. Extended Quota Mode is free but requires approval, and commercial apps must comply with Spotify's Developer Terms.
Last.fm API
The Last.fm API is free for non-commercial use. Commercial applications require a separate licensing agreement with Last.fm, the terms of which are not publicly available.
Key Features Breakdown
Playlist Management
- MusicAPI: Create, read, update, and delete playlists across all 12+ platforms with a single API call. Transfer playlists between services seamlessly.
- Spotify API: Full playlist CRUD, but limited to Spotify. Collaborative playlists and playlist images are supported.
- Last.fm API: No playlist management capabilities.
Music Search and Discovery
- MusicAPI: Cross-platform search that returns unified results from multiple streaming services.
- Spotify API: Powerful search with audio features and recommendations, but limited to 10 results per query since February 2026.
- Last.fm API: Tag-based discovery and similar artist lookups powered by community scrobbling data.
User Library Access
- MusicAPI: Access liked tracks, saved albums, and listening history across all connected platforms.
- Spotify API: Full library access for Spotify accounts, including saved tracks, albums, and recently played.
- Last.fm API: Detailed scrobbling history and listening statistics, but no direct library management.
Music Metadata
- MusicAPI: Comprehensive track, album, and artist metadata normalized across platforms.
- Spotify API: Rich metadata including audio features (danceability, energy, tempo), popularity scores, and album artwork.
- Last.fm API: Community-driven metadata including tags, biographies, and listener counts.
Which API Should You Choose?
Choose MusicAPI if:
- Your app needs to support multiple streaming platforms
- You want a single integration instead of managing multiple APIs
- You need playlist transfer or cross-platform synchronization
- You value transparent, predictable pricing and rate limits
- You want to reduce development time by up to 90%
Choose Spotify Web API if:
- Your app exclusively targets Spotify users
- You need Spotify-specific features like audio analysis or recommendations
- You're building a non-commercial project with fewer than 5 users
- You don't need cross-platform compatibility
Choose Last.fm API if:
- You're building around listening history and scrobbling data
- Your focus is music discovery through community-driven metadata
- Your project is non-commercial
- You need aggregated listening statistics rather than direct platform integration
The Verdict
For most developers building modern music applications, MusicAPI offers the best balance of coverage, simplicity, and scalability. Instead of stitching together multiple single-platform APIs (and dealing with each one's authentication quirks, rate limits, and data formats), MusicAPI gives you a unified interface across 12+ services.
The Spotify API remains powerful for Spotify-only use cases, but its recent restrictions (5-user dev mode cap, endpoint deprecations, reduced search limits) make it increasingly challenging for new projects. Last.fm fills a niche for scrobbling data and community-driven discovery, but lacks the playlist management and multi-platform features that most modern apps require.
Ready to simplify your music integration? Get started with MusicAPI for free and connect to 12+ streaming platforms with a single API.
Frequently Asked Questions
Is MusicAPI a replacement for the Spotify API?
MusicAPI is not a direct replacement — it's a unified layer that sits on top of multiple music platforms, including Spotify. If you need Spotify-specific features like audio analysis, you may still want direct Spotify API access. However, for common operations like playlist management, user library access, and music search, MusicAPI covers Spotify and 11 other platforms through a single interface.
Can I use the Spotify API for commercial projects?
Yes, but you need to apply for Extended Quota Mode and comply with Spotify's Developer Terms. Since February 2026, dev mode is limited to 5 users and requires a Premium account, so commercial projects need approval before they can scale.
Is the Last.fm API still maintained?
Yes, the Last.fm API is still active and maintained. However, it hasn't seen major feature additions in recent years. Its strengths remain in scrobbling data and community-driven music metadata.
How does MusicAPI handle rate limiting across multiple platforms?
MusicAPI manages rate limits internally for each connected platform. Your app only needs to stay within MusicAPI's own request quotas (based on your pricing plan), and MusicAPI handles the complexity of respecting each underlying platform's limits.
What happens if I exceed my MusicAPI request quota?
On paid plans, overage requests are billed at €0.40 per 1,000 additional requests. On the free plan, requests beyond the 800/month limit are rejected until the next billing cycle.