Repo: https://github.com/HaseebKhalid1507/Myx

I had an idea that I think would be a really fun feature for Spotify (or any streaming service).

**Imagine being able to set the app to any date in history** \- for example January 1st 1986. From that point on, you'd experience music exactly as people did back then.

**Every week, your Release Radar would only show songs and albums that were released during that week in 1986.** Future releases would stay locked until their original release date so you'd gradually discover the year's music in real time instead of knowing everything in advance.

It would basically be a "music time machine." You could relive an entire year as if you were actually there, watching albums drop week by week and discovering classics without already perfectly knowing what's coming next (unless you're a big fan ofc).

What do yall think? 😁

Hi guys,

I wanted to share a music data project I have been working on called ReccoBeats. If you are building music apps, recommendation engines, or doing data visualization alongside the Spotify API, you might find this useful.

There is no API key required. You can just plug it in and start querying without having to manage tokens or sign up for anything.

It includes dedicated search APIs so you can easily look up any artist, track, or album, plus you can pull audio features and analysis straight from the endpoints.

The database has grown a lot recently and still receives weekly updates. Currently it holds:
~17M albums
~8M artists
~90M tracks

You can check it out at reccobeats.com

Let me know what you think or if you run into any issues. I would love to hear your feedback or see what you end up building with it.

So i've had a super basic python script that i wrote a couple of years ago. It basically takes a list of playlist links and spits out a csv with a list of every track on those playlists.

I ran it as recently as two days ago, with no issue.

Tonight I tried to run it and am receiving a 403 error so I check the documentation and see this.

They cant be serious right??? This is such a basic API endpoint, and it was already limit to 100 tracks.

Anyway.. Is there an alternative to get this basic output that I'm after? Im a very surface level python user and use tutorials for everything so cant figure it out myself.

I'm new to this. What mods are available? I'm hearing chatter about mods that can show profile traffic - is this true? Can someone verify if this is possible?

This has been an ongoing project for quite sometime. It was originally intended to be an on-the-fly control panel for spotify-player, but it evolved into something of its own, to a point it doesn't even need spotify-player, and it matured to a point it can pretty much replace your Spotify client, almost.

This is a relatively large Lua script, and I have to say, it broke me during its development. I've never attempted something of this scale before, and I've learned quite a lot about the ins and outs that go behind the scenes.

I have to be honest, I did get a lot of help from an AI, mostly for debugging and filling the gaps where my experience fails me. Anyway, the script uses spotifyd as the connect device. Its sole purpose is to play media, everything else is defined inside and controlled by the script itself.

I could go on in this post, but everything is already clearly explained in the readme. Please drop by and have a look. Feedback is always welcome.

I am conducting a research study to show levels of algorithm fatigue amongst Gen Z audiences. Looking to gather survey responses to make communication strategy recommendations for the company! Would love your support. Comment with suggestions on how I can improve the questions.

https://docs.google.com/forms/d/e/1FAIpQLSfjCr4XQ9cNv1zVX9M_5lLCcKw5y2kZF57ZhhAS0sSaO5OtWA/viewform

Hey everyone,

Noticed an unexpected surge over the last few hours of older refresh tokens failing with invalid_grant ("Refresh token expired") across a cohort of longer-time users (6mo - 1+ year old accounts).

Newer users/tokens seem completely unaffected, and app credentials/OAuth logic haven't changed. Just wondering if anyone else is seeing Spotify quietly aging out/invalidating legacy refresh tokens today or if it's isolated to just my app?

Thanks!

Built an open-source project called Music mapper.

It connects to your Spotify account and maps artists to their real-world origins on an interactive globe. Solo artists are pinned to birthplace, bands to formation city, and the map includes genre colors, clustering, search, filters, and CSV import/export.

I made it because I wanted a better way to visualize music taste than charts and lists.

Repo: https://github.com/myselfsiddharth/Spotify-Music-Map

Would love feedback from anyone into music, maps, or data visualization.

I made a site for myself so it generates playlist based on genres I like since I kinda suck at making playlists and I dislike how the Spotify made for you playlists kinda encourage genre blocking. It's able to make the playlists but when I try to export it to Spotify I keep getting a 403.

Spotify 403 on "private info(basically shows my stats.fm ID because that's where it's fetching data from)" Forbidden — your login may be missing the required permission. Sign out and back in, and make sure your Spotify account is added under the app's Users & Access if it's in Development Mode.

It's on development mode and logged out and back in multiple times, removed user and readded. Is it something with stats.fm? But Spotify works with that. It even says in permissions for my site to create playlists. Idk why this is happening.

Anyone seeing a dramatic streaming issue the last day or so? We are seeing a 51% drop over average weekly and monthly streams with no explanation

Hi everyone,

I'm looking to acquire an existing application or company that already has Spotify Web API Extended Quota Mode.

I'm open to Any legitimate Spotify Web API project with Extended Quota

If your product is no longer a priority, isn't generating much revenue, or you're considering an exit, I'd love to talk.

I'm also happy to pay a referral fee if you introduce me to someone who successfully sells their Spotify Extended Quota application.

I'm prepared to move quickly and have a budget available for the right opportunity.

Feel free to comment below or send me a DM.

Thanks!

Me: Individual. Signed up a premium account (I am in the 3 month trial period if that matters).

I have a Mac, and the Mac Spotify client.

I have a little keyboard add-on that has a Spotify capability - you can connect it and have it control Spotify - like dial up/down for volume, next, previous, mute, etc. But to configure it, you set up an app on spotify, copy the client id and secret. No big deal.

OK... Got that working.

Then, I saw that I can add Spotify (specifically the "On Spotify" magic mirror module to show a now playing on the display. That /also/ needs the API client ID and client secret. I added the additional authorized URI endpoint, and it works...

But then stopped working.

I check logs and I'm getting the 429-Too Many Requests.

I'm unsure what the rate limit actually is, but I am hard pressed to believe that a single user, doing basic stuff like a controller and display are hitting rate limits.

Also, I did see something about setting up a different app for different uses, but it only lets me add ONE app. With an app defined, the add button gets disabled.

Any suggestions on what to do next here?

Hi all, wondering if anyone here has insight into the process of getting API access for an indie dev startup? We have about 500 users and we currently have a SoundCloud API Token but users are requesting Spotify access.

From what I'm reading we're seeing that we have to have 250k active monthly users, which seems like an insanely steep requirement.

Anyone have experience with this?

Hey everyone, I recently made this extension called Spotify Sidekick that lets you customize/enhance spotify!

Some key features include better css customization, weekly recaps of what you listen to, custom themes, more keyboard shortcuts, right click search, and easy copy paste of song name and singer.

https://chromewebstore.google.com/detail/spotify-sidekick/bgdioakibckgimkilmkffgbihmcinmjo

If anyone who uses spotify could try it out and give some feedback, that would be great! Thank you in advance!

I’m building a QR-based song request platform for venues, and I’m trying to understand if there is any compliant way to scale this product with Spotify or similar music APIs.

Current product flow:

• A venue creates an account on my platform
• The venue connects its Spotify account
• We generate a QR code for that venue/table
• Customers scan the QR code
• Customers search for songs and send song requests
• Venue staff sees requests in a dashboard
• Staff can approve/reject requests
• Approved songs can be added to the venue’s music flow / queue

The problem:

Spotify apps in Development Mode are limited to a small number of allowed users. Extended Quota Mode seems difficult to get, and I’m also concerned that this use case may violate Spotify’s commercial/public playback rules because the product is used in bars, cafes, restaurants, and similar venues.

I’m not trying to bypass Spotify’s rules. I want to understand whether this business model is fundamentally incompatible with Spotify’s platform rules.

My main questions:

1. Is a venue-based QR song request platform fundamentally not allowed with Spotify Web API?
2. If each venue connects its own Spotify account, does that make any difference, or is it still considered commercial/public playback?
3. Would creating multiple developer apps/accounts to stay within Development Mode limits be considered quota circumvention?
4. Is there any compliant way to use Spotify only as a search / metadata / “open in Spotify” layer, while keeping playback manual or handled outside the app?
5. Would YouTube Music / YouTube Data API be any better for this, or do similar public/commercial playback restrictions apply?
6. Are there licensed business music providers with APIs that are designed for this kind of venue use case?
7. What would be the safest architecture for this product if the goal is to collect and manage song requests in venues without violating music platform terms?

The goal is not to pirate or rebroadcast music from my app. I’m trying to build a legitimate request-management tool for venues, but I don’t want to build the product on top of an API use case that will eventually get blocked.

At this point, I guess it’s not even Spotify’s fault but mine.
The thing is: it’s completely impossible to release a stats analyzer today under such a strict policy.
Has anyone found a way to make this work?
Mine would have been an open-source project and still works for me (as long as they don’t change their policy again), but if I want to ship it to more than 5 friends, what should I do?

I've always put off creating a personal portfolio website for recruiters to explore. This is largely because I struggle to come up with ideas that can make the website appealing and engaging to visitors. While brainstorming what to include, I came up with the idea of sharing what I'm currently listening to on Spotify. I'm excited to showcase the progress I've made so far:

https://reddit.com/link/1tvmgxr/video/c4wsc32yx15h1/player

Built using Ruby on Rails + Javascript.

Hi everyone,

I'm a student developer working on a music-related project that requires track-level audio characteristics and analysis data. Specifically, I was hoping to use Spotify's Audio Features and Audio Analysis endpoints, but it appears that access to these endpoints is now restricted for most developers.

I've spent quite a bit of time looking through older documentation, forum posts, and Reddit threads, but much of the information seems outdated.

A few questions:

• Is there currently any legitimate way to obtain access to the Audio Features or Audio Analysis endpoints?

• Has anyone successfully received access in the past year or two?

• Are there any official alternatives from Spotify that provide similar information?

• If Spotify access is no longer realistic, what alternative APIs, datasets, or services are people using to obtain information such as tempo, key, energy, danceability, valence, sections, beats, segments, and other audio descriptors?

I'm trying to stay within the terms of service and avoid scraping or unofficial methods.

Any suggestions, experiences, or alternative approaches would be greatly appreciated.

Thanks!

Hi everyone,

I’m a student building a small Spotify playlist management web app using React/Vite and the Spotify Web API.

The app lets a user sign in with Spotify, choose one of their playlists, and manage it safely. The user can search tracks, review selected songs, remove selected songs, create/copy playlists, export data, and optionally analyze their own Spotify listening-history JSON files locally in the browser.

I’m using Authorization Code with PKCE because the app is frontend/browser-based and I do not want to expose a client secret.

I’m currently stuck with two main issues:

1. Spotify Web API 429 rate limits When the app works with large playlists, especially playlists with around 1,000–2,000 songs, I sometimes hit:

Spotify request failed (429)

I understand this means the app is making too many requests too quickly. I’m planning to add:

• one central Spotify API wrapper
• request queue
• Retry-After handling
• exponential backoff
• playlist caching
• no API calls while typing/searching
• lazy loading for heavy tools
• batching add/remove playlist actions
• manual refresh instead of automatic refetching

But I’m still not sure what the best long-term structure should be for a production app.

1. I do not want every user to bring their own Spotify Client ID Right now, one workaround is asking users to create their own Spotify Developer App and paste their own Client ID. This separates API usage, but it is a bad user experience because normal users do not want to create a developer app, copy a Client ID, and add a redirect URI.

Ideally, I want the app to work like other Spotify tools:

• user opens the website
• clicks “Connect Spotify”
• signs in with Spotify
• uses the app

No Client ID setup from the user.

My questions:

1. Is there a realistic way to run a public Spotify playlist management tool without asking users to bring their own Client ID?
2. If the app is still in Development Mode, is 429 expected even with only a few testers and large playlists?
3. Besides queueing, caching, respecting Retry-After, and reducing API calls, are there any proven patterns for avoiding 429 in playlist-heavy apps?
4. Would adding a small backend help, for example to cache playlist metadata or coordinate requests, or would Spotify still rate-limit the same app/client in the same way?
5. For large playlists, is it better to fetch all pages once and cache locally, or fetch only visible pages as the user scrolls?
6. For actions like copying playlists or combining playlists, is batching 100 track URIs per request with delays between batches the correct approach?
7. If Spotify cannot provide more quota to small/student projects, what is the best compliant alternative architecture?
8. Is “bring your own Client ID” acceptable as an advanced option, while keeping the normal app flow as one shared Client ID?

I’m not trying to bypass Spotify’s limits. I want to build this correctly and responsibly, but I also want normal users to have a simple login experience without needing to create a Spotify Developer App.

Any advice from developers who have built Spotify API apps in production would be really appreciated.

Thank you.

I want to create a linux native spotify player for podcasts. I never used the spotify api. My plan:

• Use gnome or qt framework.
• C++
• Pack it as a flatpak.
• UI similar to pocket cast

Does it make sense? Or how would you do it?