Spotify data API
Look up public Spotify artists, albums, and tracks by ID or share URL. Structured JSON you can store next to TikTok and YouTube creator rows — without a Spotify developer app for read-only catalog enrichment.
3 endpointsWhy teams use Social Fetch for Spotify
Creator and brand graphs often stop at social handles and miss the Spotify artist ID that labels actually use for campaigns, playlisting, and catalog ops. A TikTok sound attribution or a pasted open.spotify.com link sits in a CRM note with no stable id, monthly listeners, or release context attached.
Scraping Spotify web pages yourself means brittle HTML, region quirks, and a second auth stack beside the scrapers you already run for TikTok and Instagram. Spotify's official Web API is the right tool when you need playback, user libraries, or playlist write scopes — but it expects a Spotify developer app, quotas, and OAuth flows that enrichment jobs rarely want just to resolve a public artist card.
Social Fetch exposes three Spotify GETs under one marketplace key: artist, album, and track. Pass a Spotify id or a public `open.spotify.com` URL, then read the shared `{ data, meta }` envelope — `data.lookupStatus`, `meta.requestId`, `meta.creditsCharged` — the same shape as every other platform on the catalog. Pair an artist lookup with TikTok profile or YouTube channel rows when you are building music-aware creator intelligence.
What Spotify data can you get?
- Artist cards by Spotify artist id or artist URL — display name, bio, followers, monthly listeners, related artists, discography counts.
- Album lookups with label, release date, cover art, credited artists, and an ordered tracklist.
- Track metadata — title, duration, album context, credited artists — from a track id or share link.
- Accept either a raw Spotify id or a public `open.spotify.com/{artist|album|track}/…` URL on each route.
- Same Social Fetch API key and response envelope as TikTok, YouTube, Instagram, and the rest of the marketplace.
Spotify API endpoints
Grouped by capability from the live API catalog. Open an endpoint page for parameters and examples — credit notes come from OpenAPI pricing extensions.
Profiles & channels
1Content
2How to call the Spotify API
1. Create an API key
Sign up at Social Fetch and copy a key (`sfk_…`). New accounts get 100 free credits — enough to smoke-test artist, album, and track GETs against live catalog data.
2. Call a Spotify route
Send `GET /v1/spotify/artist` (or `/album`, `/track`) with `x-api-key` and either the entity id query param or a public Spotify URL. Use the TypeScript SDK or curl in production jobs; keep the playground for one-off checks in the app.
3. Join music ids to social rows
Branch on `data.lookupStatus` before writing. Persist the Spotify artist/album/track id on the same person or campaign record as TikTok and YouTube handles. Log `meta.requestId` for support; bill from `meta.creditsCharged`.
How much does the Spotify API cost?
Spotify artist, album, and track routes charge 1 credit per successful completed lookup. Credits never expire on pay-as-you-go packs. Confirm every response with `meta.creditsCharged` — that field is the billing source of truth.
Social Fetch vs the official Spotify API
Spotify Web API is Spotify's official product for apps with developer credentials, rate limits, and user OAuth. Use it when you need playback control, user library scopes, playlist management, or other authorized features. Social Fetch Spotify routes are public catalog enrichment: id or share URL in, structured JSON out, no Spotify developer app and no creator OAuth. Choose official for write and private-user cases; choose Social Fetch when Spotify is one enrichment source beside social networks on a shared marketplace key.
Spotify API FAQ
Is there a Spotify scraper API / Spotify data API?
Yes. Social Fetch provides REST routes for public Spotify artists, albums, and tracks. Authenticate with a Social Fetch API key (`x-api-key`); you do not need a Spotify developer app for these public catalog lookups.
What Spotify data does Social Fetch cover?
Three operations under the Spotify tag: `GET /v1/spotify/artist`, `GET /v1/spotify/album`, and `GET /v1/spotify/track`. Artist responses can include metrics (followers, monthly listeners), related artists, and discography counts. Album responses include release metadata and an ordered tracklist. Track responses include title, duration, album context, and credited artists. Exact fields are on each endpoint page and in `/docs/api`.
Do I need a Spotify developer app or OAuth?
Not for Social Fetch public catalog routes. You only need a Social Fetch API key. Spotify Web API with a developer app and OAuth remains the path for playback, user libraries, and playlist write scopes.
Can I access user playlists or listening history?
No. These routes return public catalog metadata only. Private libraries, recently played, and playlists you manage require Spotify's official Web API with the appropriate user scopes.
What identifiers do Spotify routes accept?
Each route accepts either a Spotify entity id (`artistId`, `albumId`, or `trackId`) or a public `https://open.spotify.com/...` URL for that entity type. One identifier per request — do not send conflicting id and URL values on the same call.
How much does the Spotify API cost on Social Fetch?
You buy credit packs (or use the 100 free signup credits). Artist, album, and track lookups cost 1 credit each on a successful completed request. There is no required monthly subscription for pay-as-you-go packs. Always check `meta.creditsCharged`.
Spotify Web API vs Social Fetch — which should I use?
Use Spotify Web API when you need official quotas, playback, user-authorized features, or playlist management. Use Social Fetch when you want public artist/album/track enrichment without standing up a Spotify developer app, or when you already normalize social and music data through Social Fetch's shared envelope across platforms.
Does HTTP 200 always mean the artist, album, or track was found?
No. HTTP 200 means the request finished. Check `data.lookupStatus`: `found` means you got catalog data; `not_found` means the id or URL did not resolve. Persist `meta.requestId` when you need to debug a miss.
Can I use Spotify routes from agents or MCP?
Yes. The same operations appear as typed MCP tools and can be reached via Ask (`POST /v1/ask`) for plain-English exploration. For production jobs, pin the typed GET paths (`/v1/spotify/artist`, `/album`, `/track`) so routing stays explicit.
Is scraping Spotify data legal?
Social Fetch returns publicly visible catalog data. You are responsible for how you use it under Spotify's terms, applicable law, and your own compliance review. We do not give legal advice.
Start with Spotify data
Create an account, spend the 100 free credits on live Spotify routes, then buy a pack when the JSON fits your pipeline. Credits do not expire on pay-as-you-go packs.