Skip to content

Feature request: Chaptarr integration for ebooks/audiobooks #92

Closed

Description

@Erik-White

Is your feature request related to a problem? Please describe.
I would like to use Chaptarr for book management

Describe the solution you'd like
Integration of Chaptarr as an service for eBooks and Audiobooks

Describe alternatives you've considered
It seems to work normally (sync, createing requests etc) when added as a Bookshelf service, but it would be nice to have it officially supported in addition to Bookshelf

Additional context

Activity

  1. snapetech commented on Aug 21, 2026

    @snapetech
    Collaborator

    I think this is going to work out of the box, with no additonal code changes required. I'll add some documentation around the use of it.

  2. snapetech commented on Aug 21, 2026

    @snapetech
    Collaborator

    Ok maybe some small changes, different API paths and such, but I'll have this built into the next release later today.

  3. Erik-White commented on Aug 21, 2026

    @Erik-White
    Author

    Amazing, thanks!

  4. MrMxyzptlk commented on Aug 30, 2026

    @MrMxyzptlk

    I just tried this on the latest build, but was unable to add Chaptarr for eBooks and AudioBooks. I ended up adding it to two instances of Readarr instead. Please let me know how you add Chaptarr for both.

  5. snapetech commented on Aug 31, 2026

    @snapetech
    Collaborator

    Update: I went back and fixed this properly in ca0784e1.

    The earlier "works out of the box" update was a little premature. Chaptarr needs different API paths for ebooks and audiobooks, and the old integration was also losing the media-specific monitoring/search options and sending the wrong queue request. The fix detects Chaptarr, uses the right provider path, preserves those options, handles Chaptarr responses, and loads the queue with the pagination it expects.

    I tested it against a real Chaptarr instance: lookup, adding a book, updating an existing book, monitoring/search, and queue loading all worked. This is included in v3.12.9.

    One caveat: Chaptarr is currently returning no ebook lookup results from its own API, so I could fully verify the audiobook flow. That looks like the upstream issue tracked in Chaptarr #67; SeerrNG now avoids treating audiobook results as ebooks.

  6. snapetech commented on Aug 31, 2026

    @snapetech
    Collaborator

    I've submitted an upstream patch to Chaptarr to fix this issue.

    Chaptarr/chaptarr#114

  7. Erik-White commented on Aug 31, 2026

    @Erik-White
    Author

    I've had a chance to update to 3.12.9 and try it out, but I'm also having issues.
    Requesting a book initially appears to succeed, but the request is failed if I look under Requests. The spinner also just remains indefinitely

    Image Image
  8. Erik-White commented on Aug 31, 2026

    @Erik-White
    Author

    There is nothing in the logs unfortunately
    This is with a Chaptarr instance that is v0.9.911.0

  9. snapetech commented on Aug 31, 2026

    @snapetech
    Collaborator

    I reproduced this against the exact Chaptarr 0.9.911.0 image.

    The problem is split between Chaptarr and SeerrNG. Chaptarr’s ebook-scoped lookup returned no rows for “The War of the Worlds”; its native lookup returned audiobook metadata instead. v3.12.9 then filtered that result out because it was labeled audiobook, so the request worker had nothing to add and later marked the request Failed. That is why the success toast and failed Requests card could both appear.

    I fixed the SeerrNG side. When an older Chaptarr build has no results for the requested format, SeerrNG now keeps an addressable native result as the add seed and explicitly sends the requested format to Chaptarr. I tested the real 0.9.911.0 container: the ebook add completed, monitoring was repaired, and the follow-up search was sent successfully. There is also a regression test for this exact empty-ebook-index behavior.

    Commit:
    4873365

    The missing ebook lookup data is tracked upstream here:
    Chaptarr/chaptarr#67
    Chaptarr/chaptarr#114

  10. snapetech commented on Sep 4, 2026

    @snapetech
    Collaborator

    This request is complete in SeerrNG. Chaptarr support, format-specific API paths, monitoring/search handling, queue compatibility, and the older Chaptarr empty-ebook-index fallback are implemented and covered by regression tests. The fixes landed in commits ca0784e1 and 4873365c, and were released in v3.12.9. The remaining empty ebook index is tracked upstream in Chaptarr #67, with the SeerrNG-side workaround already in place. Closing as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions