Skip to content

Jellyseerr Integration

Jellyseerr mode creates requests instead of adding content directly to Radarr or Sonarr. Jellyseerr owns approval, quotas, notifications, quality profiles, and root-folder selection.

  1. Configure Radarr and/or Sonarr inside Jellyseerr.
  2. Copy the Jellyseerr API key from Settings → General.
  3. Ensure Blockbusterr can reach the Jellyseerr URL.
jobs:
mode: jellyseerr
jellyseerr:
url: http://jellyseerr:5055
api_key: your_jellyseerr_api_key

When the containers share a Docker network, use the container name rather than localhost.

An API key normally creates requests with its own permissions. You can set a Jellyseerr user ID:

jellyseerr:
url: http://jellyseerr:5055
api_key: your_jellyseerr_api_key
user_id: "2"

Alternatively, local login credentials can be used for request creation:

jellyseerr:
url: http://jellyseerr:5055
api_key: your_jellyseerr_api_key
request_credentials:
email: user@example.com
password: your_password
jobs:
mode: jellyseerr
sync_interval: 24h
list:
- id: family-movies
name: Family Movies
enabled: true
type: popular
source: simkl
media: movie
limit: 30
sync_interval: "0 8 * * *"

The job’s discovery source does not change the request workflow. Blockbusterr fetches candidates, applies the global movie filters, and creates Jellyseerr requests for accepted items.

Blockbusterr does not provide Jellyseerr with score-based approval thresholds. To control approval:

  • Configure movie and show auto-approval on the Jellyseerr user.
  • Configure request quotas in Jellyseerr.
  • Use Blockbusterr’s global filters to reject unwanted candidates before requesting them.
  • Verify the URL from the Blockbusterr host or container.
  • Verify the API key in Jellyseerr.
  • Confirm the selected user can request the media type.
  • Check Activity Entries for filtered, duplicate, or failed items.
  • Confirm the job’s discovery provider is configured.