Artist
1 credit/v1/spotify/artistOne artist: id, name, follower count, monthly listeners, genres, and related artists. Address by Spotify artist URL or id.
id or url
Spotify APIScrape public Spotify data with one API
Fetch public Spotify artists, tracks, albums, playlists, and podcasts as structured JSON with one SocialCrawl API key. Same Author and Post schema as every other platform. Reads are priced in credits.
/v1/spotify
6 active endpoints
- GET /v1/spotify/artist
- GET /v1/spotify/track
- GET /v1/spotify/album
- GET /v1/spotify/search
- GET /v1/spotify/podcast
- GET /v1/spotify/podcast/episodes
What Spotify endpoints does SocialCrawl ship?
Six live read endpoints for public Spotify data. Artists, tracks, albums, playlist search, podcast shows, and podcast episodes. Data API only. No playback control, no private library, no Spotify user OAuth in your client.
Track
1 credit/v1/spotify/trackOne track: name, artists, album and cover art, duration, play count, and sharing links.
id or url
Album
1 credit/v1/spotify/albumOne album: title, artists, release date, cover art, copyright info, and the tracks on it.
id or url
Playlist search
1 credit/v1/spotify/searchPlaylists matching a keyword. Playlist results only: tracks, artists, albums, and podcasts are not returned as search hits today.
query
Podcast show
1 credit/v1/spotify/podcastOne podcast show: id, name, description, and cover art. Address by Spotify /show/ URL or id.
id or url
Podcast episodes
1 credit/v1/spotify/podcast/episodesEpisodes for one podcast: title, release date, duration, cover art, and short preview audio URL. Page with the cursor from the previous response.
id or url, cursor
Spotify API6 endpoints supported
View docsReturns a Spotify artist's details: id, name, follower count, monthly listeners, genres, and related artists.
Use it when you have an artist id or URL and want the artist itself rather than one of their tracks or albums.
1 credit
GET/v1/spotify/artist?url=https%3A%2F%2Fopen.spotify.com%2Fartist%2F0cGUm45nv7Z6M6qdXYQGTX
$ curl https://www.socialcrawl.dev/v1/spotify/artist?url=https%3A%2F%2Fopen.spotify.com%2Fartist%2F0cGUm45nv7Z6M6qdXYQGTX \
-H "x-api-key: sc_YOUR_API_KEY"idle
// Running this live needs your own API key. Hit "Try it" to see an example responseHow the Spotify API works
Spotify is a normal SocialCrawl social surface. You call GET /v1/spotify/… with an API key, spend credits on live misses, and get a single JSON envelope back. No Spotify developer app in your client. No second SDK.
Authenticate every call
Send your key in the x-api-key header. No Spotify OAuth flow in your app. The same key works across the SocialCrawl catalog.
GET with query params
All Spotify routes are GET. Pass url, id, query, and cursor as query strings. We validate formats before charging.
Pay in credits, not seats
Every Spotify read costs 1 credit on a live miss. Cache hits cost 0. Empty or hard failures refund.
Read one JSON envelope
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Episode lists carry pagination when more remain.
The usual integration chain
Most products resolve an artist or show, pull catalog items, then deepen only the tracks or episodes that matter.
01Artist or show
GET /v1/spotify/search?query=…Author-shaped artist or podcast: followers, genres, cover art
Resolve the URL or id once before listing catalog content.
02Track or album
GET /v1/spotify/podcast?url=…Post-shaped track or album with play counts and artwork
Open a single song or the full record when list rows are not enough.
03Playlist search
GET /v1/spotify/podcast/episodes?url=…Playlist hits for a keyword
Discover editorial or community playlists without a track id.
04Podcast episodes
GET /v1/spotify/track?url=…Episode list with preview URLs and durations
Page a show after you know the podcast identity.
request
GET /v1/spotify/artist
?url=https://open.spotify.com/artist/…
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here
# podcast chain
GET /v1/spotify/podcast?url=https://open.spotify.com/show/…
GET /v1/spotify/podcast/episodes?url=…response envelope
{
"success": true,
"data": {
"id": "0TnOYISbd1XYRBk9myaseg",
"username": "artist_slug",
"display_name": "Example Artist",
"followers": 1200000,
"url": "https://open.spotify.com/artist/…",
"ext": {
"genres": ["pop"],
"popularity": 82
}
},
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}What lands in data
Field names match the rest of SocialCrawl where archetypes align. Artists and shows map to Author. Tracks, albums, and episodes map to Post leaves.
Authorartist, podcast
id, username/display_name, avatar_url, bio, followers, url, ext (monthly listeners, genres, related artists)
PostList / Posttrack, album
track, album, or episode as Post: id, url, content, engagement (plays), author/artists, published_at, media ext
Playlist searchsearch, podcast/episodes
playlist hits for query: id, name, description, cover, owner fields when exposed
Episode listenvelope fields
items[] with title, release date, duration, cover, preview audio URL; cursor when more episodes remain
Inside the gateway
Same request lifecycle as every other /v1 platform endpoint. Spotify is not a sidecar.
- 01
Edge receives the call
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).
- 02
Validate, then debit
Registry lookup finds spotify/artist (or track, album, search, podcast). Required params and URL format checks run first. Invalid input returns 400 with no charge. Valid calls debit 1 credit atomically before upstream work.
- 03
Cache or fetch
A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: social-read upstream for Spotify routes. Retries on 5xx/network with a circuit breaker if the source is unhealthy.
- 04
Normalize and return
Upstream JSON is mapped to Author / Post / PostList (or route archetype), validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.
Billing rules that matter in production
- Standard live miss: 1 credit
- Artist, track, album, search, podcast, episodes: all 1 credit
- No advanced tier on this platform
- No premium tier on this platform
- Cache hit: 0 credits
- Empty / hard fail: auto-refund
- Bad params: 400, never charged
- No credits: 402, never charged
- Disabled routes: 503, never charged
How we get the data
Spotify is public-read music and podcast catalog data. We normalize it into the SocialCrawl schema so your code does not learn a second OAuth flow.
What Spotify is for this API
Public artists, tracks, albums, playlist search hits, podcast shows, and episodes. Read-only surface for research, monitoring, and product jobs. No private libraries and no playback control.
How SocialCrawl reaches it
Social-read upstreams behind one gateway. You send open.spotify.com URLs or ids; we fetch and normalize without a Spotify app in your client.
What leaves our edge
A unified JSON envelope: success, data, credits_used, request_id, cached. Artists and shows become Author objects. Tracks, albums, and episodes share Post leaves where archetypes align.
What we do not ship live
No write endpoints. No user library or playlist mutation. Search returns playlists only today. Prefer the registry docs for the live inventory.
field map sketch
artist / show card→ author.*artist name, followers, monthly listeners, genres
track / album / episode→ post.* + ext.*track or album title, artists, cover, play count
search playlist hits→ PostList items[]podcast episode title, duration, preview audio URL
What this API is used for
The jobs this API is most often used for.
6active Spotify endpoints in the registry
1 creditflat 1 credit per live miss
Catalog enrichment and podcast episode monitoring
Callers concentrate on artist and track detail, album pulls, playlist keyword search, and podcast to episodes chains. Public Spotify catalog reads on the shared schema with credit pricing. No Spotify developer app in your client for these public surfaces.
Artist, track, album, and show calls are typically a few seconds on live miss. Episode lists and search can be slightly slower on cold cache.
What people build with the Spotify API
The jobs Spotify data is most often used for. Each one is a full recipe with the endpoint chain and pricing.
Use case examples
Common ways teams put this data to work, and the stack each one tends to run.
Catalog enrichers
Python, workers, CMS loadsResolve artist and track URLs into structured cards. Fill internal catalogs with followers, play counts, and artwork.
Podcast monitors
Node, cron, Slack botsPoll podcast plus podcast/episodes for a fixed set of shows. Alert when new episodes publish.
Backend product jobs
Go, workers, ExplorerWire artist to track to album, or search playlists by keyword, into pipelines. Same key as the rest of SocialCrawl.
Call it in two lines
Every Spotify route is one credit per live call. Cache hits are free.
curl "https://www.socialcrawl.dev/v1/spotify/artist?url=https://open.spotify.com/artist/0TnOYISbd1XYRBk9myaseg" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/spotify/search?query=true+crime" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Endpoints
What data does the Spotify API return?
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Comparison
How does SocialCrawl compare to Spotify Web API for Spotify data?
Same Spotify data, two very different paths. Auth, rate limits, schema, and cost, side by side.
| Feature | SocialCrawl | Spotify Web API |
|---|---|---|
| Authentication | One x-api-key header | OAuth 2.0 client credentials with token refresh |
| Setup | Sign up and call, no app registration | Developer dashboard app registration before the first call |
| Rate limits | Credit-based: your only quota is your balance | Per-app rolling rate limits with 429 retry handling |
| Response schema | Unified JSON shared across 64 platforms | Well documented, but Spotify-specific objects |
| Pricing | 1 credit per request; 100 free credits on signup | Free for catalog metadata within rate limits |
| Data coverage | Artists, tracks, albums, podcasts, episodes, and search | Full official catalog plus user-authorized data |
| Maintenance | One integration covers Spotify and 63 other platforms | Separate SDK and token logic just for Spotify |
Authentication
SocialCrawl
One x-api-key header
Spotify Web API
OAuth 2.0 client credentials with token refresh
Setup
SocialCrawl
Sign up and call, no app registration
Spotify Web API
Developer dashboard app registration before the first call
Rate limits
SocialCrawl
Credit-based: your only quota is your balance
Spotify Web API
Per-app rolling rate limits with 429 retry handling
Response schema
SocialCrawl
Unified JSON shared across 64 platforms
Spotify Web API
Well documented, but Spotify-specific objects
Pricing
SocialCrawl
1 credit per request; 100 free credits on signup
Spotify Web API
Free for catalog metadata within rate limits
Data coverage
SocialCrawl
Artists, tracks, albums, podcasts, episodes, and search
Spotify Web API
Full official catalog plus user-authorized data
Maintenance
SocialCrawl
One integration covers Spotify and 63 other platforms
Spotify Web API
Separate SDK and token logic just for Spotify
FAQ
Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usHow do I get Spotify data with an API?
Send a GET request to any of SocialCrawl's 6 Spotify endpoints (including artist, track, album, search, podcast, and podcast episodes) with your x-api-key header. Each returns clean, unified JSON without OAuth flows or app registration.
Is there a Spotify data API?
Yes. SocialCrawl is a Spotify data API that returns artist, track, album, and podcast metadata, episode lists, and keyword search as unified JSON from one x-api-key. Spotify's official Web API is free and handles your own-app and user-authorized data well, but it requires app registration and OAuth token refresh before the first call. For reading public catalog metadata, SocialCrawl skips all of that: 6 endpoints at 1 credit each, with 100 free credits on signup.
Do I need OAuth or a Spotify developer account?
No. The official Spotify Web API requires app registration, OAuth token exchange, and refresh handling before your first call. SocialCrawl needs one API key, the same key that covers 63 other platforms on the same unified schema.
What Spotify data can I get?
Artist profiles with follower counts, genres, and related artists; track and album metadata including tracklists and release dates; podcast (show) details; cursor-paginated episode lists; and keyword search across tracks, artists, albums, podcasts, episodes, and audiobooks.
How much does the Spotify API cost?
Every Spotify endpoint costs 1 credit per request on the standard tier. New accounts get 100 free credits with no credit card required, so you can make around 100 calls before paying anything.
How does SocialCrawl handle Spotify rate limits?
You never deal with Spotify's per-app rate limits or 429 retry logic. SocialCrawl's upstream layer manages that for you. Your only quota is your credit balance, and repeated requests for the same resource are served from cache.
Can I use the Spotify API in production?
Yes. The endpoints are built for production workloads with consistent response times and a unified schema that stays stable even when Spotify changes its response format. One envelope, one auth model, one credit system.
What is the best Spotify scraper API?
For catalog metadata without OAuth, SocialCrawl is the simplest route: 6 Spotify endpoints (including artist, track, album, search, podcast, episodes) at 1 credit per request, with 100 free credits and no card. The official Spotify Web API is free and broader, but requires app registration, OAuth token refresh, and Spotify-only response formats.
Is scraping Spotify data legal?
SocialCrawl returns publicly available Spotify data and does not access private or login-gated content. Whether scraping fits your project depends on your use case and jurisdiction. You are responsible for complying with Spotify's terms of service and applicable data-protection laws such as GDPR and CCPA. This is general information, not legal advice.
Spotify scraping API vs the official Spotify API: what's the difference?
With SocialCrawl there is no app review or approval queue. Sign up and call Spotify endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.
Ask AI about SocialCrawl