OAuth Readiness
Back to all apps

Spotify for Developers

Generated live by the research agent (Gemini), checked 2026-10-19. Setup not tested by hand.

Building an AI agent product that connects to Spotify requires registering an app, which starts in development mode with a limit of five users. To lift these restrictions for a public audience, developers must submit an extended quota request that involves a business verification review.

Tier 5: Gated

Hands-on work
1–5 hours
Waiting for approval
0–42 days
Confidence
high

Assumes: A public AI agent application that external users connect to using their own Spotify accounts, requesting typical scopes to read and act on user data.

10 min1 hour1 workday1 week1 month6 months

Solid dark bar: your hands-on work. Amber: the minimum wait. Hatched: the range sources disagree on, or an open-ended wait.[2]

Biggest blocker: Spotify only accepts extended quota applications from legally registered organizations operating an active and launched service, which blocks individuals and pre-launch products.[2]

Why tier 5? Set by: partner or paid access.
The tier is computed from these seven facts by a fixed rule, not chosen by the AI. High: the gates that set this tier are backed by the provider's own docs or our own test.
Self-serve credentialsYesDevelopers can create credentials directly through the Developer Dashboard.[2]
Limits until reviewedYesNewly created apps begin in development mode limited to 5 authenticated users who must be added to an allowlist.[2]
Provider reviewYesMoving from development mode into extended quota mode for a wider audience requires an app review by Spotify's app review team.[2]
Security assessmentNoNot mentioned in the official process: quota extension requests require an application form and compliance evaluation rather than a formal security assessment.[2]
Business verificationYesAs of May 15th 2025, Spotify only accepts applications from established business entities (legally registered businesses or organisations) operating an active and launched service.[2]
Mandatory feesNoNot mentioned in the official process: there are no application fees listed for requesting quota extensions.[2]
Partner or paid accessYesQuota extension applications are restricted to organizations and require an active, launched service available in key markets.[2]

Composio has no managed app here (spotify), so you need your own OAuth app before users can connect at all. Start the slow steps first. Managed auth list

If your case is different

Internal or Development Use
For apps under construction or used by up to 5 developers and beta testers, the app can remain in development mode without business verification or review.

Steps

Agent steps an AI agent can do or draft for you. You steps that need your identity, accounts, legal authority or a real demo.

  1. Register the application

    You

    Log in to the Developer Dashboard to create a new application and obtain client credentials.[2][5]

  2. Configure redirect URIs and scopes

    Agent

    Set up the redirect URI allowlist and configure the required authorization scopes for the application.[1][3][4]

  3. Test in development mode

    You

    Add up to five test users to the app allowlist to test functionality under development mode limits.[2]

  4. Submit quota extension application

    You

    Fill out the 4-step questionnaire via company email in the Developer Dashboard to request extended quota mode.[2]

  5. Wait for review

    AgentWait

    Wait for Spotify's app review team to evaluate the app and provide feedback by email, which can take up to six weeks.[2]

What you will need

  • Established Business Entity (legally registered business or organisation)[2]
  • Operating an active and launched service available in key Spotify markets[2]
  • App owner must have a Spotify Premium account for development mode apps to function[2]

Nuances that catch people out

  • Users may be able to log into a development mode app without being allowlisted, but API requests with their access token will receive a 403 status code error.[2]
  • As of May 15th 2025, Spotify only accepts partner and quota applications from organizations, not individuals.[2]

Evidence

What we could not verify

  • Exact hands-on hours required to implement the integration were estimated due to a lack of explicit timing details in the documentation.

Sources

Each quote was checked by code against the live page. “Not found on page” means the quote may be paraphrased, so treat that claim with care.

  1. Scopes | Spotify for Developers
    Provider docschecked 2026-10-19
  2. Quota modes | Spotify for Developers
    Provider docsQuote found on pagechecked 2026-10-19
    This review process can take up to six weeks.
  3. Authorization Code with PKCE Flow | Spotify for Developers
    Provider docschecked 2026-10-19
  4. Authorization Code Flow | Spotify for Developers
    Provider docschecked 2026-10-19
  5. Authorization | Spotify for Developers
    Provider docschecked 2026-10-19