fix(templates): lidarr/organizr uses v3 endpoints that don't exist on Lidarr (v1-only API)#96
Merged
nzxl101 merged 1 commit intoJul 12, 2026
Conversation
…idarr's lidarr/organizr.json grants /api/v3/rootfolder, /api/v3/calendar, and /api/v3/queue — none of which exist on Lidarr. Lidarr's API is exclusively v1 (namespace Lidarr.Api.V1; confirmed RootFolderController, CalendarController, and QueueController all live under Lidarr.Api.V1 in Lidarr/Lidarr), unlike Radarr/Sonarr/Whisparr which are v3. Every other lidarr/*.json template in this repo correctly uses /api/v1/*. Content is otherwise identical to radarr/organizr.json (same 3 endpoints, same methods), confirming this was copied from the radarr template without updating the API version prefix — every request Organizr sends against a Lidarr instance through this template currently 404s.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
`lidarr/organizr.json` used `/api/v3/*` (rootfolder, calendar, queue), which don't exist on Lidarr - its API is exclusively v1 (confirmed via the `Lidarr.Api.V1` namespace on `RootFolderController`/`CalendarController`/`QueueController`).
Content was byte-identical to `radarr/organizr.json` otherwise - a copy-paste that never updated the version prefix. Every request Organizr currently sends against Lidarr through this template 404s.