Turn public Spotify pages into structured JSON: track and album metadata, artist profiles with follower and monthly-listener counts, and the contents of public playlists.
Spotify exposes a rich layer of public catalog metadata across tracks, albums, artists, and editorial or user playlists. The Spotify Scraper API resolves this public surface into validated JSON, including track durations, release dates, artist follower counts, and playlist tracklists.
It is scoped to publicly visible metadata only, never private listening history or account data. The API is ideal for music-discovery tools and catalog dashboards that need consistent artist, album, and playlist structure at scale.
# POST a target — get validated JSON back
curl https://api.crawlzo.com/v4/scrape \
-H "Authorization: Bearer $CRAWLZO_KEY" \
-d '{
"url": "https://www.spotify.com/",
"type": "title",
"geo": "us"
}'
// ← response
{
"status": "ok",
"data": {
"title": "...",
"year": 2024,
"rating": 8.4,
"votes": 184220,
"genres": ["Drama"],
"runtime_min": 128
}
}Spotify data parsed into clean, validated JSON. Pull any group below on its own, or combine them in a single request.
Music catalog and playlist enrichment
Artist follower and listener tracking
Public playlist placement monitoring
Discovery and recommendation datasets
Public metadata only: track, album, and artist details, follower and monthly-listener counts, and the tracklists of public playlists. We never touch private accounts or listening history.
Structured JSON straight from the API, or pushed to your stack natively — S3, BigQuery, Snowflake, Postgres, Kafka, or any HTTPS webhook. Call it from Python, Node, Go, Rust, or any HTTP client. The data lands where your pipeline already lives.
No. You pay for valid, schema-passing rows only. Retries, blocks, CAPTCHAs, and 5xxs are on us. If a run doesn't return data that conforms to the schema, it isn't billed.
Every request routes through the same engine behind our Web Unblocker API: compliant residential IPs, real browser fingerprints, TLS-level evasion, behaviour modelling, and built-in CAPTCHA solving. Hard targets become routine.
Yes. We respect robots policies, rate budgets, and ToS-aware allow/deny lists. We deliver and move on — no row-level retention beyond your replay window. GDPR DPA, PII redaction, and custom data residency available on request.