Skip to content

Spotify

View Spotify music catalog, manage users' libraries, get recommendations and more

Open documentation ↗
OAuthHTTPSNo CORSMusic

Verified today: 100% uptime

Is Spotify free, and does it need an API key?

Still free to register, but much more restricted since February 2026. The app owner needs Spotify Premium, a development-mode app is capped at five users and one client ID, and several endpoint families were removed. Extended access is only for registered businesses with at least 250,000 monthly active users.

Price
Restricted
API key
Required, free signup
Free limits
Development mode: 5 users per app and at most 10 search results per page.

How to get a Spotify API key

  1. Log in to the Spotify developer dashboard with an account that has Premium.
  2. Create an app to get a client ID and client secret.
  3. Exchange them for an access token with the client-credentials or authorisation-code flow.
Get a key ↗

Send it as Authorization: Bearer ACCESS_TOKEN

Checked by hand on 2026-10-24 against Spotify: February 2026 Web API dev mode changes, Spotify: updating the criteria for extended access and TechCrunch: Spotify requires Premium for developer mode. Providers change their terms, so confirm on their own pages before you commit.

API key

Required, free signup

HTTPS

Supported

Browser calls

No, needs a proxy

Status

Live · 100/100

Overview & Architectural Role

Spotify provides programmatic access to view spotify music catalog, manage users' libraries, get recommendations and more. Delivered over secure HTTPS protocols, it exposes structured endpoints designed to integrate cleanly into modern frontend frameworks, backend microservices, and automated data pipelines without requiring local database provisioning.

Who it is built for

Engineers building web dashboards, mobile applications, CLI utilities, or background cron workers in need of reliable music data feeds.

Architectural Advantage

Consuming Spotify removes the operational overhead of running custom scrapers, orchestrating headless browser fleets, or manually seeding and maintaining a local database. Instead of reverse-engineering volatile DOM layouts or dealing with anti-bot IP blocks, your application connects directly to a standardized JSON interface designed for backend ingestion with consistent schema schemas. Dedicated authentication ensures rate quotas and credential tracking per project environment.

What our checks found

Health score
100/100
Reliability
100%
Average latency
1072ms

Last checked 2026-10-24. Measured independently, not self-reported by the provider.

Core Use Cases & Architecture Ideas

Practical real-world patterns for integrating Spotify into software systems.

Automated SaaS Feature Integration

Embed data and functionality from Spotify directly into application onboarding, profile enrichment, or reporting dashboards.

Architecture: Backend service worker fetches Spotify during user workflows, caches responses in Redis, and hydrates UI state.

Scheduled Reporting & Monitoring Bot

Periodically extract updates from Spotify to generate daily digests, analytics reports, or Slack notifications.

Architecture: A scheduled GitHub Action or cron worker executes a lightweight script calling Spotify, formatting markdown summaries for stakeholders.

Rapid Prototyping & Hackathon Showcase

Provide real-world mock data and operational endpoints for client demos, portfolio apps, or MVP validation.

Architecture: Static client SPA queries Spotify directly to populate mock dashboards, graphs, and interactive UI states without a custom backend.

Code Implementation Examples

Production-ready starting templates with error handling for Spotify.

// Uses OAuth. Exchange your credentials for an access token first.
// Modern native fetch with error handling
async function callApi() {
  try {
    const response = await fetch('https://developer.spotify.com/api/v1/resource', {
      method: 'GET',
    headers: {
      'Authorization': 'Bearer YOUR_ACCESS_TOKEN',
      Accept: 'application/json',
    },
    });

    if (!response.ok) {
      throw new Error(`HTTP ${response.status}: ${response.statusText}`);
    }

    const data = await response.json();
    console.log('Response payload:', data);
    return data;
  } catch (error) {
    console.error('API request failed:', error);
    throw error;
  }
}

// callApi();

This API does not send CORS headers, so a browser will block a direct call from your front end. Call it from your server, or put a small proxy in front of it.

Response Payload & Live Testing

Inspect the expected JSON structure returned by Spotify.

Expected JSON Response Payload

Authentic sample payload structure to evaluate schema attributes before integration.

{
  "status": 200,
  "api": "Spotify",
  "endpoint": "/spotify",
  "data": {
    "id": 101,
    "title": "Spotify Sample Payload",
    "description": "View Spotify music catalog, manage users' libraries, get recommendations and more",
    "verified": true,
    "category": "Music",
    "updated_at": "2026-10-24T07:39:57.357Z"
  },
  "meta": {
    "response_time_ms": 1072,
    "cached": false
  }
}
Format: application/json

Integration Considerations & Best Practices

Technical factors to keep in mind when integrating Spotify into production environments.

Implement In-Memory or Edge Caching

Avoid triggering rate limits on public feeds by caching response payloads in Redis, Vercel KV, or standard HTTP Cache-Control headers with a 5-to-15 minute TTL.

Shield Credentials in Backend Route Handlers

Never expose private API keys in client-side JavaScript or bundle environments. Proxy requests through a Next.js API route or serverless backend to keep secret keys out of public DevTools inspection.

CORS Proxy Required for Browser Frontend Calls

This API does not send Access-Control-Allow-Origin response headers. Direct fetch() calls from browser JavaScript will fail due to Same-Origin Policy. Route your calls through a server backend or lightweight edge proxy.

Validate HTTP Status Before Parsing JSON

Always inspect response.ok before executing response.json(). Upstream services returning 4xx or 502 Bad Gateway often serve HTML error pages, which cause syntax errors when parsed as JSON.

Where this listing comes from

Aggregated from 2 public sources (public-api-lists, public-apis), then normalised and checked by us.

Report an issue with this listing ↗

Other Music APIs

See all 45 →

Openwhyd

Music

Openwhyd is a free and open-source music curation service that allows users to create playlists of music tracks from various streaming platforms (YouTube, SoundCloud, Vimeo, Deezer…) and to discover the music posted by other users.

No keyCORSHTTPS

Verified today: 100% uptime

View Details

Gaana

Music

API to retrieve song information from Gaana

No keyHTTPS

Verified today: 100% uptime

View Details

JioSaavn

Music

API to retrieve song information, album meta data and many more from JioSaavn

No keyHTTPS

Verified today: 100% uptime

View Details

SearchLy

Music

Similarities search based on song lyrics

No keyHTTPS

Verified today: 100% uptime

View Details

Spotify — common questions

Answered from what our own scheduled checks found, not from the provider's marketing.

Is the Spotify API free?

Still free to register, but much more restricted since February 2026. The app owner needs Spotify Premium, a development-mode app is capped at five users and one client ID, and several endpoint families were removed. Extended access is only for registered businesses with at least 250,000 monthly active users. Checked on 2026-10-24.

Does Spotify need an API key?

Yes, and it is free: you get one by signing up. Send it as Authorization: Bearer ACCESS_TOKEN.

How do I get a Spotify API key?

1. Log in to the Spotify developer dashboard with an account that has Premium. 2. Create an app to get a client ID and client secret. 3. Exchange them for an access token with the client-credentials or authorisation-code flow.

What are the Spotify API rate limits?

Development mode: 5 users per app and at most 10 search results per page.

Can I call Spotify from browser JavaScript?

Not directly. Spotify did not return CORS headers when we checked, so the browser will block your page from reading the response even though the request itself succeeds. Call it from a server, or put a small proxy in front of it.

Is Spotify still working?

Yes, as of 2026-10-24. Our automated check reached Spotify and recorded a 100% reliability score with a median response time of 1072 ms. We re-check on a schedule, and this page updates with the result.