Spotify Scrapper

Hey music innovators! 🎧

If you're using our CMS to power your audio platform, you know Spotify integration is essential for rich features like featured playlists, artist discovery and automated content. But recently, Spotify locked down key endpoints (editorial playlists, related artists, top tracks, etc.), breaking traditional integrations.

Our solution? A powerful scraper plugin that bypasses these limits through Spotify's unofficial APIs!

Here's why our approach works - and why continued support keeps it running smoothly:

How Our Scraper Actually Works (Corrected Flow)

Let me clarify the exact process when your CMS needs restricted Spotify data:

1. Your CMS requests restricted data (e.g., "Artist Top Tracks")
2. Your scraper plugin contacts OUR API server (with your proxy details)
3. We launch Puppeteer (headless browser) using YOUR proxy to visit Spotify
4. We extract Spotify's security keys (tokens, headers, cookies)
5. We return these keys to YOUR SERVER. They will work for 1-2 hours
6. Your PHP CMS uses php with these keys + proxy to directly fetch data from Spotify's unofficial API

✅ Result: You get the data Spotify tried to block 😁

❌ Without this? Immediate 403 errors from Spotify

Why Simple Scrapers Fail

But why did we make it so complicated? Why not another simple scrapper like YouTube scrapper or SoundCloud scrapper?

Most scrapers rely on:

• Public APIs or open HTML
• Static headers and user-agents
• Direct requests via PHP or cURL

Well, Spotify's unofficial API is heavily protected by hashes, tokens, sessions and etc. A simple scrapper could not reliably do the job. We tried

Why can't we let you run the Puppeteer yourself?

Technically, you could - but experience tells us this path leads to pain (for you) and chaos (for us). Here's why we manage the browser automation:

• Server Nightmares:
• You'd need Node.js, Chrome, Puppeteer + 27 dependencies perfectly configured alongside your PHP stack. One version conflict = broken scraper.
• The FFmpeg, youtube-dl Trauma:
• Around 30% of our support tickets are "Why won't FFmpeg convert my files?" despite it being a third party tool which makes it fall outside the scope of support. Despite including an static version and test button for it
• Envato's Support Boundaries:
• Per marketplace rules, we can't debug your Node/Chrome/Puppeteer/server setup. We'd have to decline your requests and the plugin might go unused by many

Why This Can't Be Completely Free (The Reality)

Browser automation is resource-intensive. Unlike simple PHP scrapers, Puppeteer requires:

• Full Chrome instances running ($0.20 per instance)
• Daily code updates to counter Spotify's changing defenses
• Dedicated servers to handle parallel requests

In other words, we have to pay some $ every time your server sends a request to our server to ask for extracted keys. To keep this sustainable, only users with active support (or within their 6-month free support period) can use this feature. Support can be renewed easily at any time from Codencanyon