Jellyseerr / Seerr Integration

Jellyseerr mode creates requests instead of adding content directly to Radarr or Sonarr. It supports both Jellyseerr and Seerr because they expose the same compatible request API. The selected request server owns approval, quotas, notifications, quality profiles, and root-folder selection.

The configuration key and job mode remain named jellyseerr for backward compatibility; point the URL at either a Jellyseerr or Seerr server.

Prerequisites

1. Configure Radarr and/or Sonarr inside Jellyseerr or Seerr.
2. Copy its API key from Settings → General.
3. Ensure Blockbusterr can reach the request server URL.

Configuration

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.

Request as a specific user

An API key normally creates requests with its own permissions. You can set a Jellyseerr/Seerr 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

Caution

Keep the API key and optional login credentials private. Store them only in your local configuration or environment.

Example job

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 job’s assigned movie or show rule set, and creates Jellyseerr/Seerr requests for accepted items.

Approval behavior

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

• Configure movie and show auto-approval on the Jellyseerr/Seerr user.
• Configure request quotas in Jellyseerr or Seerr.
• Use the job’s assigned Blockbusterr rules to reject unwanted candidates before requesting them.

Troubleshooting

• Verify the URL from the Blockbusterr host or container.
• Verify the API key in Jellyseerr or Seerr.
• 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.