Pull any SoundCloud track or artist page as JSON: play count, likes, reposts and comments, track duration and upload date, and artist follower totals.
SoundCloud is the home of independent and emerging artists, where engagement is measured in plays, likes, reposts, and comments rather than chart positions. The SoundCloud Scraper API extracts track and artist pages into validated JSON with play counts, engagement totals, and upload metadata.
It is designed for A and R scouting and grassroots music-trend tools that track momentum before an artist breaks through. Play and engagement counts resolve at request time and an artist's track catalog paginates in full.
# POST a target — get validated JSON back
curl https://api.crawlzo.com/v4/scrape \
-H "Authorization: Bearer $CRAWLZO_KEY" \
-d '{
"url": "https://www.soundcloud.com/",
"type": "title",
"geo": "us"
}'
// ← response
{
"status": "ok",
"data": {
"title": "...",
"year": 2024,
"rating": 8.4,
"votes": 184220,
"genres": ["Drama"],
"runtime_min": 128
}
}SoundCloud data parsed into clean, validated JSON. Pull any group below on its own, or combine them in a single request.
A and R scouting and talent discovery
Play-count and engagement momentum tracking
Independent-artist trend detection
Upload velocity and catalog monitoring
Yes. Each track returns its play count, likes, reposts, and comment count, along with duration and upload date, and each artist returns their follower total and track catalog.
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.