Spotify Play Count Scraper

Spotify Play Count Scraper exports timestamped public Spotify track play counts, artist monthly listeners and album metadata from watchlist URLs. Use the results for music reporting and compare saved snapshots in your own workflow. Exact metrics are returned only when Spotify exposes them.

Quick start

Add a public Spotify track URL, keep the first request small and run the Actor. Open the dataset when the run finishes.

{
  "trackUrls": [{"url": "https://open.spotify.com/track/3n3Ppam7vgaVa1iaRUc9Lp"}],
  "maxItems": 1,
  "includeRelatedTracks": false
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose an example to start with a small, preconfigured input.

• Monitor Spotify track play counts — Collect timestamped public track metrics.
• Monitor Spotify artist monthly listeners — Collect an artist's public audience snapshot when available.
• Export Spotify album track performance — Request album metadata and exposed related track counts. No aggregate album play count is provided.

What you get

• Track metrics: exact public play counts when available.
• Artist metrics: monthly listeners when exposed.
• Album context: identity, artist and release metadata.
• Timestamped provenance: Spotify IDs, canonical URLs, capture timestamps and availability warnings.
• Optional related tracks: additional public track rows exposed in the requested page's data.

Who is it for?

• Music marketers retaining public track observations around campaigns.
• Label and artist-management researchers maintaining known public watchlists.
• Music-data analysts comparing source-exposed metrics with capture times.
• Reporting developers joining public entity IDs in their own snapshot datasets.

How you can use the data

• Inspect the existing Mr. Brightside track target. Use its Quick start URL with one watchlist input and related tracks off. Keep spotifyId, snapshotAt, metricAvailability and warnings with any exact exposed play count, without replacing unavailable counts with zero.
• Record an artist's public audience snapshot. Use the existing artist URL with a one-target cap. Monthly listeners are source-exposed artist metrics, not private Spotify for Artists data or the same measure as track plays.
• Keep album metadata separate from track counts. Use the existing album recipe when release context or exposed related tracks are needed. Album rows have no aggregate public play count, and related track rows are separate saved records with isTarget false.
• Compare your own watchlist captures. Join entityType and spotifyId with snapshotAt in your destination. Keep target provenance and unavailable outcomes so a missing observation is not called a fall in popularity or confirmed deletion. The Actor captures snapshots rather than calculating growth, history or campaign impact.

Input settings

Setting	API key	Description
Track URLs	trackUrls	Public track URLs for exact play counts when exposed.
Artist URLs	artistUrls	Public artist URLs for monthly listeners when exposed.
Album URLs	albumUrls	Public album URLs for album metadata, not aggregate album counts.
Maximum metric rows	maxItems	Limits valid watchlist URLs processed. Default 10, range 1–1000.
Include related tracks	includeRelatedTracks	Include exposed related tracks. Default false.
Skip unavailable metrics	failOnUnavailableMetric	Skip unavailable target rows and continue. Default false.

Supply at least one valid track, artist or album URL. Multiple lists can be combined. Track targets are processed before artists, then albums. The Actor uses direct public access and has no proxy setting.

Artist and album input recipes

For artist monthly listeners, use:

{"artistUrls":[{"url":"https://open.spotify.com/artist/0C0XlULifJtAgn6ZNCW2eu"}],"maxItems":1}

For album metadata and any exposed related tracks, use:

{"albumUrls":[{"url":"https://open.spotify.com/album/4piJq7R3gjUOxnYs6lDCTg"}],"maxItems":10,"includeRelatedTracks":true}

Output data

Illustrative output example, not a current measurement. Counts and timestamps below are not live values.

{
  "entityType": "track",
  "spotifyId": "3n3Ppam7vgaVa1iaRUc9Lp",
  "url": "https://open.spotify.com/track/3n3Ppam7vgaVa1iaRUc9Lp",
  "name": "Mr. Brightside",
  "artistNames": ["The Killers"],
  "albumName": "Hot Fuss",
  "playCount": 3427230508,
  "monthlyListeners": null,
  "releaseDate": "2004-06-15T00:00:00Z",
  "snapshotAt": "2026-08-26T00:00:00.000Z",
  "scrapedAt": "2026-08-26T00:00:00.000Z",
  "metricAvailability": "available",
  "sourceInput": "https://open.spotify.com/track/3n3Ppam7vgaVa1iaRUc9Lp",
  "warnings": [],
  "isTarget": true
}

Field	Description
entityType, spotifyId, url, name	Spotify entity identity and canonical URL.
artistNames, albumName, releaseDate	Public track, artist, or album metadata when applicable.
playCount	Public exact track play count. null when Spotify does not expose an applicable value.
monthlyListeners	Public artist monthly-listener metric. null for non-artist rows.
snapshotAt, scrapedAt	ISO timestamps for the metric capture.
metricAvailability, warnings	Explicit availability state and any source limitation.
sourceInput, isTarget	Requested input provenance and target-versus-related-track indicator.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once after initial page setup succeeds. If setup fails before that point, this event is not reached.

The item event is charged for each saved dataset row, including related tracks and saved metadata rows whose metric is unavailable. Skipped targets do not produce an item charge. This Actor does not save separate error rows.

See the live Pricing tab for current rates and discounts.

Tips for best results

• Start with one track. Check the returned fields before expanding your watchlist.
• Keep capture timestamps. Use snapshotAt when comparing exports collected at different times.
• Use track URLs for track counts. Album rows do not contain an aggregate play count.
• Leave related tracks off for a watchlist-only export. Enable them only when you want additional rows.

Limits and caveats

Only public Spotify data is supported. The Actor does not access Spotify for Artists, listener accounts, private analytics or user libraries. No Spotify credentials are accepted.

Invalid or wrong-type URLs are ignored. If no valid URL remains, the run fails before browsing. Public pages can change or omit metrics, and missing values are never substituted with zero.

maxItems limits the watchlist URLs processed and constrains related-track additions. With related tracks enabled, later requested targets can still add rows beyond that number, so it is not a strict total-output or spending cap.

Unavailable metrics are preserved as nullable values unless you choose to skip them. Completed extraction with no usable rows, skipped unavailable metrics and confirmed unavailable targets succeed with an empty dataset. RUN_SUMMARY in the run's key-value store reports each target's outcome and the run reason, without adding diagnostic dataset rows. Failed or unstarted targets are listed separately in PENDING_WORK. Useful mixed-batch rows are preserved. Inaccessible targets are not assumed private or deleted.

Invalid input, browser/setup failure, systemic request or response failures, a cutoff before any target completes, and storage or billing failures still fail the run. Suspected extraction defects retain diagnostic telemetry. Successful empty handling does not establish that a Spotify extraction route has been restored. Artist and album coverage depends on what the public page exposes, so start with a small sample.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~spotify-play-count-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"trackUrls":[{"url":"https://open.spotify.com/track/3n3Ppam7vgaVa1iaRUc9Lp"}],"maxItems":1}'

# After the returned run succeeds, use its defaultDatasetId:
curl "https://api.apify.com/v2/datasets/$DATASET_ID/items" \
  -H "Authorization: Bearer $APIFY_TOKEN"

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/spotify-play-count-scraper').call({
  trackUrls: [{ url: 'https://open.spotify.com/track/3n3Ppam7vgaVa1iaRUc9Lp' }],
  maxItems: 1,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/spotify-play-count-scraper').call(run_input={
    'trackUrls': [{'url': 'https://open.spotify.com/track/3n3Ppam7vgaVa1iaRUc9Lp'}],
    'maxItems': 1,
})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Spotify Play Count Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Spotify Play Count Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/spotify-play-count-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Spotify Play Count Scraper by Fetch Cat, or give it the identifier fetch_cat/spotify-play-count-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Spotify Play Count Scraper to retrieve https://open.spotify.com/track/3n3Ppam7vgaVa1iaRUc9Lp with a one-target cap and related tracks off. Keep capture time, exact public count when exposed and availability warnings without substituting zero.”
• “Collect the public monthly-listener snapshot for https://open.spotify.com/artist/0C0XlULifJtAgn6ZNCW2eu with a one-target cap and related tracks off. Keep source identity and capture time without claiming private artist analytics.”
• “Retrieve metadata for https://open.spotify.com/album/4piJq7R3gjUOxnYs6lDCTg with a one-target cap and related tracks off. Keep release context and unavailable-metric reasons without inventing an aggregate album play count.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I get Spotify play counts through an API?

Yes. Supply public track URLs through the API examples above. Exact counts depend on Spotify exposing them.

Can I export artist monthly listeners?

Yes, when the public page exposes the metric. It is not private Spotify for Artists analytics.

Why is an album's play count null?

Spotify does not expose one aggregate public album count. Album rows provide metadata instead.

What happens when a metric is unavailable?

The Actor can preserve a metadata row with availability warnings or skip it. Completed extraction with no usable rows, skipped unavailable metrics and confirmed unavailable targets can succeed empty. Invalid input, setup or systemic failures, and a cutoff before any target completes still fail. Check RUN_SUMMARY for the reason.

Does this monitor changes automatically?

Each run captures a snapshot. Save and compare datasets in your own workflow to identify changes.

How is usage charged?

The start event covers startup after initial setup, and item covers saved rows. See the live Pricing tab above.

Can an AI assistant use it?

This public, limited-permission Actor supports the hosted MCP setup above. The assistant retrieves data and performs any comparison or summarization afterward.

What if I need broader Spotify metadata?

See Spotify Scraper in Related Actors. This Actor is focused on public music-metric watchlists.

Related Actors

• Spotify Scraper — export broader public Spotify entity metadata when you need more than monitoring metrics.
• SoundCloud Tracks Search Scraper — search public SoundCloud tracks for cross-platform music research.
• YouTube Video Details Scraper — export public YouTube video metadata for video-performance workflows.
• YouTube Channel Details Scraper — collect public channel metadata for creator monitoring.
• YouTube Playlist Videos Scraper — export public playlist video metadata.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥