Skip to content

Usable in hosted app, outside of CLI? #15

Description

@kirk-marple

Hi Spotify team, thanks for releasing this.

We’re exploring whether Save to Spotify can be integrated into a hosted app flow where an end user connects their own Spotify account via OAuth, then our app saves generated audio episodes to that user’s Spotify.

The CLI uses:

  • built-in public client ID
  • sts-content-management
  • PKCE + DPoP
  • loopback redirect URI

Our product flow would require a hosted HTTPS callback URL, not localhost/paste-back.

A few questions:

  1. Is sts-content-management available to third-party Spotify Developer apps, or is it currently limited to the published Save to Spotify CLI client?
  2. Can a hosted app use its own Spotify client ID with this backend API?
  3. Is there a supported way to register/approve a hosted redirect URI for Save to Spotify usage?
  4. Is the https://saveto.spotify.com/api/v1 backend intended as a stable integration surface for apps, or only for the CLI?
  5. If this is not supported today, is there a partner/app-review path for hosted integrations?

Our goal is user-delegated auth: each user logs into their own Spotify account and approves the required permissions; we store the resulting token in our account connector and use it to save generated audio to their Spotify.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions