Announcements

Help Wizard

Step 1

NEXT STEP

Updating the Criteria for Web API Extended Access

Updating the Criteria for Web API Extended Access

Hey, I created this thread to get your feedback on our blog post around changes to the Web API extended access criteria, which will take place on May 15th.

 

Please share any of your thoughts on this change in the comments below. All of your feedback will be reviewed and compiled so I can share directly with the S4D team.

 

Whilst I won’t be replying to individual pieces of feedback in this thread, please know that everything shared here will be read and considered. Any related threads or questions posted elsewhere on this topic will be merged here so everything is in one place.

 

Thanks for taking the time to share your thoughts.

 

Update:

 

  • Sharing some clarification that developers with existing quota moda extensions will keep their extension if they are actively using the Web API and remain in compliance with our Developer Terms. This update only applies to new developers in Dev mode seeking extended access
  • As outlined in our blog post, if you've submitted your application before May 15th, we are committing to reviewing your submission based on prior criteria, whether you hear from us before that date or not.
  • The criteria for the new process can be found HERE.
Reply
161 Replies

I'm confused how an application that relies on Spotify is supposed to get 250k MAUs.

 

Either it doesn't rely on Spotify at all during it's growth and only adds integration later as an afterthought, or it remains forever a development project.

 

In other words, you only want partnerships when it exclusively benefits you to take advantage of another app's success, rather both parties being able to grow together. 

 

Anyway, I wonder how many open-source libraries and tools others developed Spotify took advantage of when it was a small and growing app, or even now as a mega-monolith. My guess is a whole lot of them. 🙂

I have a useful update. I've contacted Tunebat.com for their music recognition tool – SongStats. They actually have a working API that can be utilized for this purpose. This is a very cheap alternative for most developers:

https://rapidapi.com/music-metrics-music-metrics-default/api/spotify-audio-features-track-analysis

I hope this helps.

Suggested posts

Let's introduce ourselves!

Hey there you,   Yeah, you! 😁   Welcome - we're glad you joined the Spotify Community!   While you here, let's have a fun game and get…

ModeratorStaff / Moderator/ 4 years ago  in Social & Random