Skip to content

fix(templates): kometa grants paged exclusion endpoints - #116

Closed
bakerboy448 wants to merge 1 commit into
Notifiarr:developfrom
bakerboy448:fix/kometa-paged-exclusions
Closed

bakerboy448 wants to merge 1 commit into
Notifiarr:developfrom
bakerboy448:fix/kometa-paged-exclusions

Conversation

@bakerboy448

Copy link
Copy Markdown
Contributor

Kometa's Radarr and Sonarr integrations fail through Starr Proxy with:

Starr Proxy: provided apikey is missing access to /api/v3/exclusions/paged
Starr Proxy: provided apikey is missing access to /api/v3/importlistexclusion/paged

ArrAPI 1.5.1 (Kometa-Team/ArrAPI 31ebbba, released 2026-10-11) reads exclusions through the paged endpoints. Kometa's develop image ships 1.5.1. On the 401, Kometa drops the Radarr connection, so every radarr_tag and radarr_add_missing builder fails with "requires Radarr to be configured".

Changes:

  • radarr/kometa.json: GET /api/v3/exclusions/paged
  • sonarr/kometa.json: GET /api/v3/importlistexclusion/paged

The unpaged GETs stay for older Kometa builds.

Tested by adding both paths to the Kometa apps on a running instance: the same Kometa keys went from proxyCode 401 to proxyCode 200 / starrCode 200 on both endpoints.

@bakerboy448

Copy link
Copy Markdown
Contributor Author

Duplicate of #114 and #115, which add the same two paths. Closing in favor of those.

Tested both paths on a running instance: the Kometa keys went from proxyCode 401 to 200 once added.

@bakerboy448
bakerboy448 deleted the fix/kometa-paged-exclusions branch October 15, 2026 01:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant