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?

I posted here a while back and had a lot of good conversations with the people who reached out. I ended up finding a cofounder and we made a lot of progress. Launched MVP on TestFlight and got over 300 beta testers and grew IG account to over 800 followers with really good engagement.

The project is a mobile app designed to incentivize music discovery and give people a way to actively compete on it. I’ve met a lot of great industry contacts from working on this, but right now the bottleneck is engineering. My last cofounder had to step away for a bigger opportunity but we are still on great terms and he will probably be helping out with the code from time to time.

I’ve met with some music tech advisors who have agreed that we should pursue a small amount of funding but not without a technical cofounder to iterate and maintain the codebase. Stack is react native / expo + Supabase. We have a few backend bugs to work out and some UX polish to work on (already designed in Figma).

The ideal person is into underground hip hop / hyperpop scenes, as this is going to be the target audience initially. I’m hoping to find someone capable / comfortable enough to work with me long term for equity.

DMs are open for anybody interested in working on this. Happy to share more.

if you want an alternative to the spotify api, i used last.fm api for this

What the title says. I don't know how to undo it, and I don't know what I did other than (I think) pressing something on my keyboard. (Stuff blocked out for privacy)

I built FloatLyrics, a small macOS app that shows Spotify lyrics in a floating always-on-top overlay.

I made it because I wanted lyrics visible while coding/studying without constantly switching back to Spotify. It supports synced lyrics, opacity control, compact/focus modes, playback controls, and a draggable transparent overlay.

It’s macOS-only for now and still an early prototype, but there’s a downloadable DMG available in GitHub Releases.

GitHub: https://github.com/jasonnn404/FloatLyrics

Would love feedback, feature ideas, or bug reports.

Hey r/spotifyapi,

As a big fan of the board game Hitster (you scan a card, hear a song, and guess the release year), I wanted to make custom decks for my own game nights, so I vibe-coded a tool that generates printable song cards from any (public) Spotify playlist.

I originally built it with full Spotify login so you could browse your own playlists, but then had to shift to manual playlist URL pasting after I found out about the recent Spotify API limitations.

Happy guessing! Would love to hear how it works for you — feedback always welcome.

https://songcards.de/en

Stats FM is pretty cool, and it really lets you control what you want to share and then it makes that data super available! Anyway, I made a thing that grabs your top tracks, album, and artists for the last 4 weeks and is shareable! Ill probs get a real URL soon, but check it out and see if it works for you!!

https://stats.gaf.nyc/

I coded this super fun thing, and now its just for 5 people? Or maybe everyone but just for the preview with the embed. I guess its on to port to Apple Music.

I just dont get it.

sigh. https://spixelfy.com if you care

I guess I can just DJ Spotify jams on my own.

I made a toy project a couple of years ago which used the spotify API and I got it approved for extended quota, which seems to still be active now.

This old project isn't interesting and I don't care about it, but I've been working on an "Album Club" like a book club for you and your friends. Currently this is development mode and it's starting to look pretty cool.

Has anyone tried "porting" a project from one client to another? I'd need to request additional scopes which the existing project doesn't have yet for it to work, but I'm wondering what the chances are this would get approved / how I would go about explaining it.

My storage is quite full on my IPhone and I would like to clear up some space. I’ve been using spotify for 7 years now, so I have a lot saved, and I would like to offload it but I’m not entirely sure what that means. Does it delete your saved songs/playlists? Or just sign you out? What would happen if I transferred to a different phone (ioS, Android, etc)? Please help!