Spotify Scraper

Export public music and podcast metadata with Spotify Scraper. Collect artist, track, album, playlist, show, episode and audiobook records with stable identifiers, images and available public metrics, then download JSON, CSV or Excel.

Direct Spotify URLs and typed Spotify URIs need no Spotify developer credentials. Keyword search requires your Spotify app Client ID and Client Secret. Each requested entity produces one metadata row, not its full child catalog.

Quick start

Paste a public Spotify URL, set a small record limit and select Start. Open the completed run's dataset to view or export the records.

{
  "startUrls": [
    {
      "url": "https://open.spotify.com/artist/06HL4z0CvFAxyc27GXpf02"
    }
  ],
  "maxItems": 1,
  "proxyConfiguration": {
    "useApifyProxy": 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.

• Export Spotify Artist Metadata — Collect an artist profile and available public audience metrics.
• Export Spotify Track Metadata — Look up a track by Spotify URI and export its catalog metadata.
• Export Spotify Podcast Show Metadata — Export a show's public description, publisher and available counts.

What you get

• Public entity metadata: artists, tracks, albums, playlists, podcast shows, episodes and audiobooks.
• Flexible direct inputs: canonical or regional Spotify URLs and typed spotify:type:id URIs.
• Catalog search: real entity records across selected types and a chosen market, using your app credentials.
• Useful fields: IDs, names, artist or publisher details, cover images, dates, durations and available public counts.
• Run context: optional RUN_SUMMARY and RUN_CHECKPOINT records describe progress, errors and remaining work.

Who is it for?

• Music researchers and artist teams: compare available public catalog and audience information.
• Playlist curators and podcast researchers: export known public entities for further review.
• Developers and data teams: enrich records with stable Spotify IDs and export structured metadata.

Input settings

Setting	JSON key	Purpose
Spotify URLs	startUrls	Public entity URLs, including regional links.
Spotify URIs	spotifyUris	Typed URIs such as spotify:track:ID.
Search queries	searchQueries	Catalog terms. Requires both app credential fields.
Search types	searchTypes	Default: track, artist, album and playlist.
Search market	market	Two-letter code. Default: US.
Results per query	maxSearchResults	Combined query cap, 1–1,000. Default: 10.
App credentials	clientId, clientSecret	Required only for search. Keep secrets private.
Maximum records	maxItems	Unique-row cap, 1–10,000. Form default: 20.
Proxy configuration	proxyConfiguration	Existing optional connection settings. Form default: disabled.

Direct URI recipe

{"spotifyUris":["spotify:track:1dGr1c8CrMLDpV6mPbImSI"],"maxItems":1,"proxyConfiguration":{"useApifyProxy":false}}

Catalog search recipe

{"searchQueries":["indie jazz"],"searchTypes":["track","artist","album"],"market":"US","maxSearchResults":10,"maxItems":10,"clientId":"YOUR_SPOTIFY_CLIENT_ID","clientSecret":"YOUR_SPOTIFY_CLIENT_SECRET"}

Provide at least one URL, URI or search query. Direct targets are processed before searches. A bare Spotify ID is ambiguous and is not accepted. Entity IDs must contain 22 base-62 characters. Search-page URLs are not entity URLs: use searchQueries and both app credentials instead. Invalid direct targets and searches missing credentials are skipped with explicit warnings in the log and RUN_SUMMARY.warnings; valid sibling inputs are preserved. When nothing valid remains, the run succeeds with no dataset rows and summary status NO_VALID_INPUT, not a claim of successful extraction. With raw API input that omits maxItems, the runtime uses 25 rather than the form's 20. Set an explicit limit for consistent requests.

Output data

Each saved row represents one entity. This synthetic shape-only example illustrates nullable metadata, not an observed extraction:

{"type":"track","id":"1dGr1c8CrMLDpV6mPbImSI","uri":"spotify:track:1dGr1c8CrMLDpV6mPbImSI","url":"https://open.spotify.com/track/1dGr1c8CrMLDpV6mPbImSI","source":"public_page","name":"Example track","artistNames":[],"albumName":null,"durationMs":null,"availableMarkets":[],"scrapedAt":"2026-10-25T12:00:00.000Z"}

Field	Description
type, id, uri, url	Entity type and canonical Spotify identifiers
name, description	Public title, description, or artist biography
artistNames, albumName	Credited artists and parent album
ownerName, publisherName	Playlist owner or podcast/audiobook publisher
trackCount	Visible track or episode count
followers, likes, monthlyListeners	Public metrics when Spotify publishes them
durationMs, releaseDate	Duration and release date at the available precision
imageUrl, previewUrl	Public cover/profile image and audio preview when available
explicit, isrc, popularity	Content and catalog identifiers when available
availableMarkets	ISO country codes returned by the public page or credential-backed search
trackNumber, discNumber, albumType, label	Additional catalog details when available
source, sourceUrl, searchQuery	Provenance for direct-page and search rows
scrapedAt	ISO timestamp when the record was created

Fields that do not apply to an entity remain null or an empty array. The dataset keeps the existing field names used by earlier versions and adds new fields without removing the old ones.

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

One start event is charged after input validation. One result event is charged for each unique dataset row saved.

Invalid input is rejected before the start charge. Failed targets, repeated attempts, duplicates and optional summary/checkpoint records are not result events. A start charge can still apply when no results are saved.

See the live Pricing tab for current rates and discounts.

Tips for best results

• Start with a known URL. Direct targets need no Spotify app credentials.
• Set explicit limits. Keep maxItems and maxSearchResults small while reviewing coverage.
• Choose the right market. Search availability depends on the selected country.
• Compare stable identifiers. Use id or uri when comparing separate exports.
• Check partial outcomes. Valid rows are preserved when an isolated target fails. Review RUN_SUMMARY when available.

Limits and caveats

• Public metadata only. No private playlists, listening history, personal libraries or account analytics.
• No song or full podcast-audio downloads. A preview URL may be returned when available.
• Playlist and album lookups produce one metadata row, not separate rows for all tracks. Visible counts may be partial.
• Field coverage varies by entity and source. Missing public fields remain null or empty. No sorting control, audio-feature analysis or complete artist discography is offered.
• An empty successful search may produce EMPTY_SOURCE. The current implementation fails when every attempted extraction has an error, including unavailable targets; recognized invalid inputs instead receive the warnings described above. Inaccessibility does not establish privacy or deletion. This documentation update does not change that behavior.
• Larger inputs may stop with remaining work recorded in RUN_CHECKPOINT. Optional summaries/checkpoints can be absent if their storage write fails.
• Search uses your app credentials and is subject to Spotify's access and market restrictions. Follow Spotify's applicable developer/content policies, including restrictions on using Spotify content for machine-learning training.

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-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"startUrls":[{"url":"https://open.spotify.com/artist/06HL4z0CvFAxyc27GXpf02"}],"maxItems":1,"proxyConfiguration":{"useApifyProxy":false}}'

After completion, fetch GET https://api.apify.com/v2/datasets/DATASET_ID/items with the returned dataset ID and secure authentication.

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/spotify-scraper').call({
  spotifyUris: ['spotify:track:1dGr1c8CrMLDpV6mPbImSI'],
  maxItems: 1,
  proxyConfiguration: { useApifyProxy: false }
});
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-scraper').call(run_input={
    'spotifyUris': ['spotify:track:1dGr1c8CrMLDpV6mPbImSI'],
    'maxItems': 1,
    'proxyConfiguration': {'useApifyProxy': False}
})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

MCP and AI agents

You can ask your AI assistant to collect data with Spotify 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 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-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 Scraper by Fetch Cat, or give it the identifier fetch_cat/spotify-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

• “Collect the public metadata for these three Spotify artist links and compare the available follower counts.”
• “Look up this Spotify track link and show me its credited artists, release date and duration when available.”
• “Export these podcast show links and prepare a spreadsheet of their names, publishers and descriptions.”

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

Do I need a Spotify API key?

Not for direct public URLs or typed URIs. Catalog search requires both Spotify app credential fields. Keep credentials out of prompts and support reports.

Can I export Spotify data to CSV or use an API?

Yes. Download the dataset or use the API examples above. JSON preserves arrays such as artist names and markets.

Can I export a playlist's full tracklist?

No. A playlist or album lookup returns that entity's metadata and available count, not each child track as a separate row.

Why are some public metrics missing?

Spotify may hide, round or regionalize fields. Public-page and catalog-search records also have different coverage. A missing field is not guessed.

What happens when one URL fails?

Useful rows from other inputs remain in the dataset. When available, RUN_SUMMARY records partial outcomes and target errors. If every attempted extraction errors, the current run fails. Recognized invalid inputs are skipped with user-visible warnings; when none are valid, the run succeeds empty with NO_VALID_INPUT.

Can I use this as a Spotify API alternative?

For known public entity metadata, direct URLs avoid the need for Spotify app credentials. It is not a replacement for account/private-data APIs or audio downloads. Use the specialist Actors below for adjacent media sources.

Related Actors

• YouTube Channel Videos Scraper — Collect recent public YouTube channel video metadata, without promising a complete historical archive.
• YouTube Video Details Scraper — Collect public YouTube video metadata and available engagement from known video URLs.
• TikTok Profile Scraper — Collect public TikTok profile details, aggregate counts and available recent video summaries.
• Reddit Scraper — Collect public Reddit posts and optional comments from supported community, search or post inputs.
• Google News Scraper — Collect public Google News feed headlines, dates and links.

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. ♥