[Enhancement]: Allow for series edits via API #3171

Open
opened 2026-04-25 00:14:03 +02:00 by adam · 3 comments
Owner

Originally created by @magrhino on GitHub (Jan 1, 2026).

Type of Enhancement

Server Backend

Describe the Feature/Enhancement

I have a tool I use to import books into audiobookshelf, I would like to be able to manually assign them to my series an existing series or create new series and assign multiple books to via the api. I do not see a way to presently do this with current docs/tools.

Why would this be helpful?

This would allow my tool to fill in missing audiobooks for users in their series with one click, and not require multiple interfaces/ matching of books via abs match with selective library editing, etc.

Future Implementation (Screenshot)

This is an api change I can't provide a screenshot.

Audiobookshelf Server Version

v2.32.1

Current Implementation (Screenshot)

This is an api enhancement not concerning the webserver but the backend api.

Originally created by @magrhino on GitHub (Jan 1, 2026). ### Type of Enhancement Server Backend ### Describe the Feature/Enhancement I have a tool I use to import books into audiobookshelf, I would like to be able to manually assign them to my series an existing series or create new series and assign multiple books to via the api. I do not see a way to presently do this with current docs/tools. ### Why would this be helpful? This would allow my tool to fill in missing audiobooks for users in their series with one click, and not require multiple interfaces/ matching of books via abs match with selective library editing, etc. ### Future Implementation (Screenshot) This is an api change I can't provide a screenshot. ### Audiobookshelf Server Version v2.32.1 ### Current Implementation (Screenshot) This is an api enhancement not concerning the webserver but the backend api.
adam added the enhancement label 2026-04-25 00:14:03 +02:00
Author
Owner

@Vito0912 commented on GitHub (Jan 1, 2026):

Everything the client does is possible with the API.

Please see the network logs of your browser. The API docs are outdated

@Vito0912 commented on GitHub (Jan 1, 2026): Everything the client does is possible with the API. Please see the network logs of your browser. The API docs are outdated
Author
Owner

@magrhino commented on GitHub (Apr 18, 2026):

Everything the client does is possible with the API.

Please see the network logs of your browser. The API docs are outdated

It appears everything is done via a network socket now and is not readable for me at least. Am I missing something?

@magrhino commented on GitHub (Apr 18, 2026): > Everything the client does is possible with the API. > > Please see the network logs of your browser. The API docs are outdated It appears everything is done via a network socket now and is not readable for me at least. Am I missing something?
Author
Owner

@Vito0912 commented on GitHub (Apr 18, 2026):

No. Websockets is mostly/exclusively for transmitting changes such as progress updates.
It receives the changes. No changes are done via it.

The API is a normal REST api

@Vito0912 commented on GitHub (Apr 18, 2026): No. Websockets is mostly/exclusively for transmitting changes such as progress updates. It receives the changes. No changes are done via it. The API is a normal REST api
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#3171