Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Plan
Premium
Country
Norway
Device
(iPhone 8, Samsung Galaxy 9, Macbook Pro late 2016)
Operating System
(iOS 10, Android Oreo, Windows 10,etc.)
My Question or Issue
We are developing and application that integrates with Spotify but have been rejected twice when requesting extension. Our application works similarly to an existing application called Rockstar Bingo that seems to have been approved. We were wondering what makes us different from them and what we can do to get approved. Thanks for the considerations.
App name: Spotify Bingo
Hi sfabriece,
I don't know how Rockstar Bingo got approved, but the current Spotify Developer Policy is from 27 May, 2021.
In this version, you can read: III. Some prohibited applications: 2. Do not create a game, including trivia quizzes.
I hope I provided you with enough information.
Cheers,
How do you handle scenarios like these? One actor obviously bases most of their business on a product on the Spotify API integration, and when another request comes in it gets denied and once confronted about the situation, there is no more to discuss but a link to a policy (read: wall) presented..
I do not understand how this policy allows some sites to get approved and some don't? Reference site https://rockstar.bingo is live and mainly operating based on its Spotify integration.
Can someone clarify how they do not get their API integration rejected if the policy prohibits this activity?
@Ximzend ?
In the past, developers didn't need to request a quota extension.
Edit: I wrote "did", but I ment "didn't".
I understand. So an audit of previously created API permissions will be made to apply to the policies set for the API?
Do you know the deadline for this clean-up?
Sorry, I have to disappoint you. I made a mistake in my previous message.
The change was made on May 27th, 2021.
I understand, but previously created API accesses will be audited to comply to the current policies? Policies are to be complied to at any current time, not just for new applicants
You have a good point. In the same blog post, you can read: "We will eventually reach out to review existing apps. There are no actions for existing apps at this stage."
I only have old app credentials (from before that date) for private use with Python script, so I don't think they will ever reach out to me.
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โฆ