Seerr, Overseerr, and Jellyseerr integration

Purpose

PlexSub uses the name Seerr for its Overseerr or Jellyseerr integration. The module shows and coordinates content requests from the Customer Portal.

It appears in PlexSub at:

• Admin: /overseerr
• Customer Portal: general status, requests, and usage

Requirements

• A working Overseerr or Jellyseerr instance.
• A URL reachable from PlexSub.
• An API key.
• Plex configured if your Seerr workflow depends on Plex.

Related variables:

• OVERSEERR_URL
• OVERSEERR_API_KEY
• OVERSEERR_WEBHOOK_SECRET
• OVERSEERR_AUTO_CREATE_USERS
• OVERSEERR_DEFAULT_PERMISSIONS

Recommended configuration

1. Confirm that Overseerr/Jellyseerr works directly.
2. Configure the internal URL PlexSub should use.
3. Add the API key.
4. If using webhooks, configure a secret.
5. Test a request with a test user.
6. Confirm the portal reflects status, usage, and duplicates correctly.

Seerr versus native Requests

PlexSub also has a native Requests module. In the service registry, Seerr is optional and experimental, while native Requests is beta, optional, and recommended.

Do not mix both flows unless you understand which module is primary in your installation.

Troubleshooting

Symptom	Likely cause	Resolution
Requests do not appear	Incorrect API key or URL	Check configuration and diagnostics.
Users are not linked	Identity differs between PlexSub and Seerr	Check email, username, and mapping.
Duplicates or unusual statuses	Mixed Seerr and native flows	Define the source of truth and review scheduled jobs.
Webhook rejected	Incorrect secret	Synchronise OVERSEERR_WEBHOOK_SECRET.