Spotify Scraper – Play Counts & Monitoring
Pricing
from $0.30 / 1,000 search results
Go to Apify Store
Complete
Complete
Complete
Complete
Complete
Complete
Complete
Complete
Complete
Spotify Scraper – Play Counts & Monitoring
Search Spotify or scrape public artists, tracks, albums, playlists, podcasts, episodes, and user profiles. Extract play counts, monthly listeners, credits, full child collections, and monitor changes—without a Spotify API key or login. Independent tool; not affiliated with Spotify.
Pricing
from $0.30 / 1,000 search results
Rating
0.0
(0)
Developer
ScrapingMonkey
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Spotify Analytics Scraper - Play Counts, Monthly Listeners and Playlist Monitoring
Extract public Spotify artists, tracks, albums, playlists, podcasts, episodes, and users into analysis-ready datasets, including metrics and relationships that are not present in basic search cards.
- Search seven public entity types with independent limits per keyword and type
- Collect artist monthly listeners, follower counts, world rank, top cities, biography, top tracks, and discography
- Extract track play counts, ISRC, market availability, album context, and grouped credits
- Paginate album tracks, playlist tracks, artist releases, public user playlists, and podcast episodes
- Extract public user followers/following, verification, profile flags, recently played artists, and large playlist libraries
- Monitor metric changes, new releases, playlist additions/removals/reordering, and new episodes across scheduled runs
- Accept Spotify URLs,
spotify:type:idURIs, bare IDs, and mixed entity batches - No Spotify Developer API key, OAuth application, login, cookies, or user-supplied proxy configuration required
- Export to JSON, CSV, Excel, XML, or access results through the Apify API
What can you do with this Actor?
| Mode | Input | Output | Best for |
|---|---|---|---|
search | Keywords plus selected entity types | Artist, track, album, playlist, show, episode, and user rows | Discovery, catalog research, playlist prospecting |
details | Public Spotify URLs, URIs, or IDs | Rich entity rows with optional flat child rows | Music analytics, metadata enrichment, catalog exports |
monitor | The same public entity inputs plus a stable monitorKey | Initialized, added, removed, and modified change rows | Scheduled artist, playlist, release, and podcast tracking |
One mode runs at a time. IDs found in search can be sent directly to details or monitor. In flat output, parent entities and their tracks, releases, related artists, public user playlists, recently played artists, or episodes become separate dataset rows with parentType, parentId, relationType, relationId, and position.
Quick start
- Open the Actor and click Try for free.
- Keep
searchselected and enter one or more search terms. - Choose entity types and set
maxResults. - Click Start.
- Preview the dataset or download it in your preferred format.
The default input searches indie pop and returns up to 50 artists, 50 tracks, and 50 playlists.
Input examples
Search artists, tracks, and playlists
maxResults applies separately to every search term and selected entity type. The example can therefore return up to 120 primary rows: 2 terms × 3 types × 20 results.
Rich details from mixed Spotify references
Monitor artist metrics and playlist contents
The first run emits an initialized change and stores a snapshot in a persistent named key-value store. Later runs using the same monitorKey emit added, removed, and modified changes.
Complete output examples
All entity serializers use fixed top-level key sets. Missing source values are represented by null, [], {}, false, or 0; entity fields are not conditionally omitted. Search rows use the same shapes as detail rows, with unavailable enrichment fields left empty. Flat child rows use the appropriate entity shape and populate the relationship fields.
Complete episode output - 34 top-level fields
The Actor returns public transcript metadata when Spotify exposes it; it does not download or reproduce full transcript or audio content.
Complete user output - 35 top-level fields
Complete change output - 15 top-level fields
changeType is initialized, added, removed, or modified. For child changes, childType and childId identify the release, track, related artist, or episode. Each side contains fixed identity keys and a values array with complete {field, value} objects for the fields that changed.
Complete error output - 13 top-level fields
Complete playlist output - 29 top-level fields
Complete show output - 37 top-level fields
Complete track output - 42 top-level fields
For standalone tracks, the six relationship fields and playlist-specific addedAt, addedBy, and relationAttributes values are null or empty. Playlist child rows populate them.
Complete album output - 37 top-level fields
Complete artist output - 39 top-level fields
What data can you extract?
The following inventory lists every top-level output key. Common relationship fields make nested Spotify collections usable in CSV, SQL, and data warehouses without losing parent context.
| Record | Complete top-level field inventory |
|---|---|
artist | recordType, sourceMode, searchTerm, parentType, parentId, relationType, relationId, position, id, uri, url, name, market, locale, scrapedAt, verified, followers, monthlyListeners, worldRank, popularity, genres, biography, biographyType, externalLinks, images, headerImages, galleryImages, topCities, topTrackCount, releaseCount, relatedArtistCount, concertCount, merchCount, saved, pinnedItem, playlists, topTracks, discography, relatedArtists |
track | recordType, sourceMode, searchTerm, parentType, parentId, relationType, relationId, position, id, uri, url, name, market, locale, scrapedAt, durationMs, explicit, contentRating, playable, playabilityReason, popularity, playCount, trackNumber, discNumber, isLocal, isrc, ean, upc, previewUrl, availableMarkets, restrictions, artists, album, images, credits, creditSources, videoAssociations, audioAssociations, addedAt, addedBy, relationAttributes, matchedFields |
album | recordType, sourceMode, searchTerm, parentType, parentId, relationType, relationId, position, id, uri, url, name, market, locale, scrapedAt, albumType, releaseDate, releaseDatePrecision, totalTracks, popularity, label, copyrights, artists, images, availableMarkets, genres, externalIds, playable, playabilityReason, isPrerelease, prereleaseEndAt, saved, courtesyLine, tracks, discs, releases, moreAlbumsByArtist |
playlist | recordType, sourceMode, searchTerm, parentType, parentId, relationType, relationId, position, id, uri, url, name, market, locale, scrapedAt, description, owner, followers, following, public, collaborative, snapshotId, revisionId, totalTracks, images, members, capabilities, format, tracks |
show | recordType, sourceMode, searchTerm, parentType, parentId, relationType, relationId, position, id, uri, url, name, market, locale, scrapedAt, publisher, description, htmlDescription, explicit, mediaType, contentType, consumptionOrder, languages, availableMarkets, copyrights, images, totalEpisodes, rating, ratingCount, topics, showTypes, trailer, playable, playabilityReason, accessInfo, gatedRelations, episodes |
episode | recordType, sourceMode, searchTerm, parentType, parentId, relationType, relationId, position, id, uri, url, name, market, locale, scrapedAt, description, htmlDescription, durationMs, releaseDate, releaseDatePrecision, explicit, contentRating, mediaTypes, playable, playabilityReason, previewUrl, images, show, restrictions, accessInfo, gatedRelations, transcripts, segments, audioUrls |
user | recordType, sourceMode, searchTerm, parentType, parentId, relationType, relationId, position, id, uri, url, name, market, locale, scrapedAt, displayName, username, socialHandle, followers, followingCount, verified, reportAbuseDisabled, hasSpotifyName, hasSpotifyImage, profileColor, allowFollows, showFollows, accountId, images, publicPlaylistCount, publicPlaylistsReturned, recentlyPlayedArtistCount, externalUrls, playlists, recentlyPlayedArtists |
change | recordType, sourceMode, monitorKey, changeType, entityType, entityId, childType, childId, changedFields, before, after, sourceUrl, market, locale, detectedAt |
error | recordType, sourceMode, input, entityType, entityId, sourceUrl, market, locale, errorType, errorMessage, httpStatus, retryable, scrapedAt |
Nested objects use stable keys:
- Images:
url,width,height. - Artist references:
id,uri,url,name. - Album references:
id,uri,url,name,albumType,releaseDate,releaseDatePrecision,totalTracks,images,artists. - Track references:
id,uri,url,name,durationMs,explicit,playable,playCount,trackNumber,discNumber,artists,album,images; playlist track references also containposition,uid,addedAt,addedBy,attributes. - Show references:
id,uri,url,name,publisher,images. - Episode references:
id,uri,url,name,durationMs,releaseDate,explicit,playable,show,images. - User references:
id,uri,url,name,username,images; full user rows also include followers/following, verification and profile flags,accountId, public playlists, and recently played artists. - Credits:
name,role,roleGroup,uri,url; credit sources:title,text,url. - Monitor sides:
recordKey,recordType,id,parentType,parentId,relationType,relationId,values; each value containsfieldandvalue.
Input parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
mode | string | Yes | search | search, details, or monitor; one mode per run |
searchTerms | string[] | Search mode | ["indie pop"] | Keywords processed independently, maximum 50 terms |
entityTypes | string[] | Search mode | artist, track, playlist | Any of artist, track, album, playlist, show, episode, user |
spotifyIds | string[] | Details/monitor | Example artist and playlist | Up to 100 public Spotify URLs, URIs, or bare IDs |
entityType | string | No | auto | Type for bare references; auto recognizes public usernames and probes ambiguous 22-character IDs, while URLs and URIs identify their type |
maxResults | integer | No | 50 | 1–5,000; per term/type in search, or per child collection/input in details and monitor |
maxConcurrency | integer | No | 5 | 1–20 concurrent inputs, enrichments, and Spotify requests |
market | string | No | US | Two-letter Spotify market and built-in Residential Proxy country |
locale | string | No | en-US | Locale for public localized text |
includeDetails | boolean | No | false | Enrich every search result with detail requests |
includeTracks | boolean | No | true | Include album and playlist tracks |
includeDiscography | boolean | No | true | Include paginated artist releases |
includeRelatedArtists | boolean | No | false | Include public related artists |
includeCredits | boolean | No | true | Include track contributors and credit sources |
includeEpisodes | boolean | No | true | Include paginated podcast/show episodes |
includeUserPlaylists | boolean | No | true | Include paginated public playlists for user details |
includeUserArtists | boolean | No | true | Include publicly visible recently played artists for users |
outputMode | string | No | flat | nested, flat, or both child representation |
monitorKey | string | Monitor mode | spotify-monitor | Stable snapshot namespace; 1–80 letters, numbers, dots, dashes, or underscores |
emitOnlyChanges | boolean | No | true | In monitor mode, omit current entity rows and return change rows only |
Use cases
Artist and label analytics
Schedule artist details to track monthly listeners, followers, world rank, top cities, top-track plays, and newly published releases. Send change rows to a warehouse or notification workflow.
Playlist research and monitoring
Find public playlists by keyword, export owners and full track lists, then monitor track additions, removals, position changes, revision IDs, and follower totals.
Music catalog enrichment
Enrich internal song or release IDs with names, artist and album relationships, ISRC/UPC values, release dates, labels, playability, market availability, artwork, and structured credits.
Podcast discovery and episode tracking
Search shows and episodes, collect ratings, publishers, topics, public access flags, descriptions, and monitor newly published episodes.
Audience and trend analysis
Compare artist reach, track plays, playlist placement, release velocity, and regional availability across recurring snapshots.
Performance and cost
The Actor is ready for Apify pay-per-event billing. Configure prices in the Actor's Pricing tab for these stable events:
| Event | Charged for |
|---|---|
search-result | One primary entity returned by search |
entity-detail | One root artist, track, album, playlist, show, episode, or user detail row |
related-item | One flat or nested track, release, related artist, public user playlist, recently played artist, or episode |
change | One initialized, added, removed, or modified monitor row |
Explicit error rows are not charged.
The main workload drivers are:
- Number of search terms multiplied by selected entity types and
maxResults. includeDetails, which adds detail requests for every search hit.- Artist discography, playlist tracks, album tracks, and show episodes.
bothoutput, which writes nested parents and separate child rows.- Residential Proxy transfer, especially the web-player bundle used during token bootstrap.
The Actor processes independent inputs and search enrichments concurrently up to maxConcurrency, while a shared request semaphore prevents request bursts above that limit. Pagination inside one logical collection remains ordered. A small test with one input and maxResults: 10 is recommended before large batches.
API usage
Replace [YOUR_USERNAME] after publishing the Actor:
Use Apify schedules for recurring monitor runs and webhooks to deliver results to Make, Zapier, n8n, Slack, Google Sheets, Airbyte, or a data warehouse.
Best for / not for
Best for: public artist analytics, playlist intelligence, catalog metadata, podcast research, scheduled change detection, and CSV/SQL-friendly exports.
Not for: private playlists, private profiles, authenticated library data, playback, DRM-protected media, full audio downloads, lyrics, full transcript downloads, or account automation.
Limits and good to know
- One mode runs at a time; multiple terms or entity inputs can be processed in one run.
- The Actor limit is 5,000 per child collection or term/type. Spotify can return fewer results or enforce a lower source-side pagination boundary.
- Public user playlist pages are deduplicated by playlist ID. Spotify filters candidates by market, so a page can contain fewer rows than its requested limit; pagination advances by the requested offset until the user limit or an empty page.
nestedreturns parent rows with child arrays.flatreturns the parent with empty child arrays plus separate child entity rows.bothreturns populated parents and separate child rows.- Public URLs and URIs identify their entity type. Bare IDs use
entityTypeor automatic endpoint probing. marketcontrols both source market filtering and the Apify Residential Proxy country. Availability and localized metadata can differ by market.- All outbound Spotify traffic uses built-in Apify Residential Proxy. The Actor exposes no direct-traffic or user proxy input.
- A sticky proxy session is retained through web-player bootstrap, token generation, and entity requests; sessions rotate after retryable blocking or network failures.
- HTTP 429 responses honor
Retry-After; expired access tokens are refreshed after HTTP 401. - Missing public source values remain
null,[],{},false, or0. Fixed entity keys are never silently omitted. - A failed input creates an explicit
errorrow while other inputs continue. The Actor fails the run only when every operation ends in a non-terminal failure. - Monitor snapshots persist by
monitorKey. Reusing a key compares against the previous successful snapshot; changing the key starts a separate baseline. - Spotify may change private web-player operations. The Actor obtains current anonymous tokens dynamically, but source changes can still require an Actor update.
Frequently asked questions
What input should I provide?
For search, provide keywords such as indie pop. For details or monitoring, provide public URLs, URIs such as spotify:track:53iuhJlwXhSER5J2IYYv1W, or bare IDs.
Can one run contain different Spotify entity types?
Yes. spotifyIds can mix artist, track, album, playlist, show, episode, and user URLs or URIs. Bare IDs need entityType: auto or a shared explicit type.
How many search rows will I receive?
maxResults is per term and selected type. Three types, two terms, and maxResults: 20 can return up to 120 primary search rows before optional detail children.
Why do some search fields contain null or empty arrays?
Basic search cards do not expose every metric. Enable includeDetails to request monthly listeners, play counts, credits, full collections, and other available enrichment.
How does monitoring work?
Run monitor repeatedly with the same monitorKey. The first run establishes a baseline; later runs compare fixed normalized rows and emit initialized, added, removed, or modified records. Apify schedules can run it hourly, daily, or weekly.
Do I need Spotify credentials, cookies, or a proxy?
No Spotify Developer credentials, OAuth application, login, or cookies are required. The Actor automatically obtains anonymous web-player tokens. Built-in Apify Residential Proxy is mandatory and configured internally.
Does the Actor download songs, lyrics, or transcripts?
No. It returns public metadata and public preview URLs when Spotify exposes them. It does not download full audio, reproduce lyrics, or retrieve full transcript bodies.
Responsible use
This Actor extracts publicly accessible Spotify metadata. Users are responsible for complying with applicable laws, privacy regulations, contractual obligations, and Spotify's terms and policies.
Spotify is a trademark of Spotify AB. This Actor is independent and is not affiliated with, endorsed by, or sponsored by Spotify.
Support
If a source response changes or a run fails, create an issue in the Actor's Issues tab. Include the run ID, mode, market, and a non-sensitive reproducible public Spotify URL. Never post access tokens, client tokens, cookies, or Apify credentials.
Local development
The Actor targets Python 3.13.
Local requests still require authenticated access to Apify Residential Proxy. The bundled free-music-master directory is retained as the MIT-licensed token-flow reference; the production Actor uses its own asynchronous implementation.
