Seerr

Seerr integration brings media request data into Librariarr for use in lifecycle rules.

Note

Overseerr and Jellyseerr were merged into the unified Seerr project on February 10, 2026. If you were previously using Overseerr or Jellyseerr, update your instance URL to point to your new Seerr installation.

Setup

1. Go to Settings → Integrations
2. Under the Seerr section, click Add Instance
3. Enter:
   • Name: A label (e.g., “Seerr”)
   • URL: Seerr base URL (e.g., http://192.168.1.100:5055)
   • API Key: Found in Seerr → Settings → General → API Key
4. Click Test Connection to verify
5. Save

What It Provides

Seerr integration makes request metadata available in Librariarr:

Data	Description
Request status	Whether media was requested, approved, or declined
Requester	Who requested the media
Request date	When the request was made
Request count	Number of requests for this media
Approval/decline date	When the request was acted on

Use in Lifecycle Rules

Seerr data is available as rule conditions in the lifecycle engine:

Field	Description	Example Use
seerrRequested	Whether media was requested	Keep all requested content
seerrRequestDate	When requested	Delete if requested over a year ago
seerrRequestCount	Number of requests	Prioritize frequently requested content
seerrRequestedBy	Who requested	Filter by specific user
seerrApprovalDate	When approved	Track time since approval
seerrDeclineDate	When declined	Clean up declined requests

Example Rule

Create a rule set to find media that was requested but never watched:

• seerrRequested equals true
• AND playCount equals 0
• AND seerrApprovalDate before 6 months ago

Security

• API keys are stored securely and never exposed to the frontend
• Connection testing uses server-side endpoints

Limitations

• Seerr data is fetched live during rule evaluation, which can be slower for large match sets
• Only one Seerr instance is supported at a time
• Request data availability depends on Seerr having been running when requests were made — historical data before Seerr was set up is not available

Note

Seerr integration is read-only from Librariarr’s perspective. Request data is used in lifecycle rules only — approving/declining requests is done through Seerr’s own interface.