[GH-ISSUE #111] API for consume/dispatch actions from third-party applications #983

New issue

Closed

opened 2026-03-14 12:49:55 +03:00 by kerem · 2 comments

kerem commented

2026-03-14 12:49:55 +03:00

Owner

Originally created by @diegoulloao on GitHub (Jan 25, 2023).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/111

Is your feature request related to a problem? Please describe.
Not a problem. is possible to dispose of a simple API to consume in order to dispatch actions from third-party applications, actions like:

get current song title that's playing
get the current playlist that's playing
play a specific song of the current playlist
go to next/previous song of the current playlist

Describe the solution you'd like
This would work sending commands to any existent instance of spotify-player running.
I would like to write a neovim plugin to control spotify-player while coding, as a widget of spotify-player for neovim, but it needs an API exposed.

E.g.

spotify_player --cmd="get-playlist"
spotify_player --cmd="play-song id"

I'm not sure if I can do this by using the service that spotify_player is using in background.
I don't know if that will get sync with spotify_player either (without hit an API for auth, etc)

I would like to get this idea working hand to hand with spotify-player, because I think is an app with a great future ahead.

Sounds crazy?

Originally created by @diegoulloao on GitHub (Jan 25, 2023). Original GitHub issue: https://github.com/aome510/spotify-player/issues/111 **Is your feature request related to a problem? Please describe.** Not a problem. is possible to dispose of a simple API to consume in order to dispatch actions from third-party applications, actions like: - get current song title that's playing - get the current playlist that's playing - play a specific song of the current playlist - go to next/previous song of the current playlist **Describe the solution you'd like** This would work sending commands to any existent instance of spotify-player running. I would like to write a neovim plugin to control spotify-player while coding, as a widget of spotify-player for neovim, but it needs an API exposed. E.g. ```bash spotify_player --cmd="get-playlist" spotify_player --cmd="play-song id" ``` I'm not sure if I can do this by using the service that spotify_player is using in background. I don't know if that will get sync with spotify_player either (without hit an API for auth, etc) I would like to get this idea working hand to hand with spotify-player, because I think is an app with a great future ahead. Sounds crazy?

kerem

2026-03-14 12:49:55 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-14 12:50:11 +03:00

Author

Owner

@aome510 commented on GitHub (Jan 25, 2023):

Hi @diegoulloao, thanks for creating this issue. Actually, I have a plan to create a similar one as I've got some related requests regarding external APIs to communicate with the app.

Related issues:

https://github.com/aome510/spotify-player/issues/103

Sounds crazy?

I thought about implementing the same thing before. I don't think it's impossible. I'll try and see xD.

@aome510 commented on GitHub (Jan 25, 2023): Hi @diegoulloao, thanks for creating this issue. Actually, I have a plan to create a similar one as I've got some related requests regarding external APIs to communicate with the app. Related issues: - https://github.com/aome510/spotify-player/issues/103 > Sounds crazy? I thought about implementing the same thing before. I don't think it's impossible. I'll try and see xD.

kerem commented

2026-03-14 12:50:16 +03:00

Author

Owner

@diegoulloao commented on GitHub (Jan 25, 2023):

Yes, excellent. LMK if you try something, you can start with simple actions to test. In parallel I can start building the bases for the neovim plugin/widget if something comes out.

@diegoulloao commented on GitHub (Jan 25, 2023): Yes, excellent. LMK if you try something, you can start with simple actions to test. In parallel I can start building the bases for the neovim plugin/widget if something comes out.