Spotify Profile Details Scraper✨
Pricing
$10.00/month + usage
Spotify Profile Details Scraper✨
🎵 Scrape any public Spotify user profile — no API key needed. Returns: 🆔 user ID · 👤 display name · 🖼️ profile image · 👥 follower & following counts · 🎤 up to 50 recently played artists with images 🎧 full playlist library with cover art & creation dates. 👥Spotify Profile Details Scraper 🎧
Pricing
$10.00/month + usage
Rating
0.0
(0)
Developer
Scrape Architect
Actor stats
0
Bookmarked
8
Total users
3
Monthly active users
14 days ago
Last modified
Categories
Share
Spotify Profile Scraper ✨
The Spotify User-Profile Scraper is a powerful, production-ready Apify Actor that extracts comprehensive public profile data from any Spotify user page — no API key, no login required. Simply provide one or more profile URLs and the Spotify User-Profile Scraper will return fully structured JSON with the user's name, follower counts, profile image, recently played artists, and complete playlist library with cover images and estimated creation dates.
⚠️ This actor is intentionally slow — please be patient. The Spotify User-Profile Scraper uses a real headless browser to render Spotify's JavaScript-heavy pages. Each profile requires multiple page loads with rendering delays. A single profile with a large playlist library can take 5–10 minutes to complete. Enabling the Include Playlists and Include Recently Played Artists options adds extra page fetches and significantly increases run time. This is expected behaviour — do not stop the run early. The actor will push your results as soon as each profile is fully scraped.
What Does the Spotify User-Profile Scraper Return?
Every result row produced by the Spotify User-Profile Scraper contains the following fields:
| Field | Type | Description |
|---|---|---|
source_url | string | Original profile URL that was scraped |
user_id | string | Spotify user ID extracted from the URL |
display_name | string | Public display name of the user |
profile_image | string | CDN URL of the user's profile picture |
followers | string | Follower count as displayed ("1,234 Followers") |
followers_count | integer | Follower count as an integer (1234) |
following | string | Following count as displayed ("56 Following") |
following_count | integer | Following count as an integer (56) |
total_public_playlists_count | integer | Total number of public playlists |
recently_played_artists | array | Up to 50 recently played artists with name, URL, and image |
playlists | array | All public playlists with title, URL, cover image, and estimated creation date |
Recently Played Artist Object
{"name": "Radiohead","url": "https://open.spotify.com/artist/4Z8W4fKeB5YxbusRsdQVPb","image": "https://i.scdn.co/image/ab676161000051..."}
Playlist Object
{"title": "fall 25","url": "https://open.spotify.com/playlist/6TWR9qj0MC1kVu3N1rwMBE","image": "https://image-cdn-ak.spotifycdn.com/image/...","created_at_proxy": "Oct 2025"}
Key Features of the Spotify User-Profile Scraper
- No API key required — the Spotify User-Profile Scraper works on fully public profile pages without any authentication
- Up to 50 recently played artists — with artist images, not just the 10 shown on the profile homepage
- Full playlist library — all public playlists scraped from the
/playlistssubpage with lazy-loaded cover images - Estimated playlist creation dates — the Spotify User-Profile Scraper visits each playlist page to extract the oldest track date as a creation proxy
- Integer + text counts — both
followers_count: 1234andfollowers: "1,234 Followers"are returned for easy filtering - Concurrent processing — up to 10 profiles scraped in parallel; each result is pushed to the dataset as soon as it is complete
- Configurable output — toggle playlists and recently played artists on/off independently
- K/M suffix support — large follower counts like
"2.4K"or"1.2M"are correctly parsed to integers
Input Configuration
The Spotify User-Profile Scraper accepts the following input fields:
| Input | Type | Default | Description |
|---|---|---|---|
profileUrls | string[] | — | Required. One or more Spotify user profile URLs |
includePlaylists | boolean | true | Scrape all public playlists with images and creation dates. ⚠️ Enabling this significantly increases run time — each playlist requires an individual page load to fetch its creation date. |
includeRecentlyPlayedArtists | boolean | true | Scrape the full recently played artists list (up to 50 with images). ⚠️ Enabling this adds an extra page fetch per profile. |
Example Input
{"profileUrls": ["https://open.spotify.com/user/7zyu0di3zv7s4seuyrp6otzzd","https://open.spotify.com/user/spotify"],"includePlaylists": true,"includeRecentlyPlayedArtists": true}
Profile URLs must be in the format
https://open.spotify.com/user/<user-id>. Artist, album, and playlist URLs are not supported by this actor.
Use Cases for the Spotify User-Profile Scraper
The Spotify User-Profile Scraper is well suited for a wide range of data workflows:
- Influencer research — identify music taste, playlist reach, and follower counts for potential collaborators
- Audience analysis — understand what artists a user's followers are listening to recently
- Playlist discovery — bulk-collect public playlist libraries from curators and tastemakers
- Music journalism — track listening habits and newly public playlists over time
- Academic research — build datasets of Spotify listening behaviour from public profiles
- Social media tooling — enrich Spotify user data with profile images and follower metrics
Example Output
{"source_url": "https://open.spotify.com/user/7zyu0di3zv7s4seuyrp6otzzd","user_id": "7zyu0di3zv7s4seuyrp6otzzd","display_name": "sun","profile_image": "https://i.scdn.co/image/ab6775700000ee85f3a000b3d4254a6ad42c633f","followers": "55 Followers","followers_count": 55,"following": "62 Following","following_count": 62,"total_public_playlists_count": 87,"recently_played_artists": [{"name": "Radiohead","url": "https://open.spotify.com/artist/4Z8W4fKeB5YxbusRsdQVPb","image": "https://i.scdn.co/image/ab676161000051..."}],"playlists": [{"title": "fall 25","url": "https://open.spotify.com/playlist/6TWR9qj0MC1kVu3N1rwMBE","image": "https://image-cdn-ak.spotifycdn.com/image/...","created_at_proxy": "Oct 2025"}]}
Performance & Cost
⚠️ The Spotify User-Profile Scraper is a slow actor by nature. Please be patient and do not stop the run early. Spotify's web app is fully JavaScript-rendered, so each page requires a headless browser with deliberate rendering delays. Turning on Include Playlists adds one extra HTTP request per playlist (to fetch creation dates), and turning on Include Recently Played Artists adds one more full page fetch per profile. Both options together represent the maximum possible run time — but they also give you the richest dataset.
| Scenario | Approx. time |
|---|---|
| 1 profile, playlists off, artists off | ~8 s |
| 1 profile, playlists off, artists on | ~13 s |
| 1 profile, playlists on (87 playlists), artists off | ~5–6 min |
| 1 profile, playlists on (87 playlists), artists on | ~6–7 min |
| 10 profiles in parallel (playlists on, artists on) | ~8–15 min |
The dominant time driver is playlist creation date fetching — every playlist in a user's library needs its own page load. With the built-in concurrency, a 100-playlist library alone takes 3–5 minutes. Users with 200+ playlists may take 10+ minutes per profile.
Tip: If you only need basic profile data (name, followers, profile image) and don't need playlists or artist history, turn both toggles off — the actor will complete in under 10 seconds per profile.
Frequently Asked Questions
Does the Spotify User-Profile Scraper require a Spotify account or API key? No. The Spotify User-Profile Scraper only accesses public profile pages that are visible to any logged-out visitor. No credentials of any kind are needed.
What profile URLs does the Spotify User-Profile Scraper support?
Only https://open.spotify.com/user/<id> URLs. Artist pages, album pages, and playlist pages are handled by a separate actor.
How many profiles can the Spotify User-Profile Scraper process at once? You can submit any number of URLs — the Spotify User-Profile Scraper will queue and process them automatically.
Why is the created_at_proxy field the estimated date and not an exact date?
Spotify does not expose playlist creation dates publicly. The Spotify User-Profile Scraper uses the oldest track-added date visible in the playlist as a reliable creation proxy.
What happens if a profile is private or does not exist?
The Spotify User-Profile Scraper will return a result object with a populated source_url and an error field describing the failure. Other profiles in the same run are not affected.
Limitations
- Only public Spotify profiles are supported
- The
recently_played_artistslist reflects what Spotify shows on the public profile page (up to 50 artists) - Playlist creation dates are estimated via the oldest visible added-date
- Spotify's page structure may change; if fields become
nullafter a Spotify update, the actor may require a maintenance update
The Spotify User-Profile Scraper is an independent tool and is not affiliated with, endorsed by, or connected to Spotify Technology S.A. Use responsibly and in accordance with Spotify's Terms of Service.