Connect Seerr
Connect Jellyseerr, Overseerr, or Seerr to Kochab for Requests under More.
Kochab uses the Seerr API (Overseerr-compatible) for Requests under More. One connection covers Jellyseerr (for Jellyfin), Overseerr (for Plex), and Seerr - they share the same API, so you add whichever one your household runs.
What Kochab exposes through Seerr
- Requests: pending, approved, available, and declined requests with approve/decline, edit, retry, and delete where the API allows
- Issues tab: open issues reported against your titles, across every configured Seerr connection
- Report an issue: file a new issue against a title from its detail screen
- Discover: Seerr contributes to Kochab’s Discover feed alongside your other configured sources
- Detail surface: pending/total request counts and link into Requests
- Push: new request and approved/denied notifications. Kochab can register the webhook after you enable notifications, when the connected account has permission
Not exposed through Seerr
User management, server/library configuration, and discovery settings stay in Seerr’s web UI. Kochab supports household sign-in using the methods enabled by your Seerr server. Now playing and library browsing use Jellyfin/Plex entries separately.
Before you start
Have your Seerr account credentials ready. For administrator API-key access instead, copy the key from Settings -> General -> API Key in the service’s web UI.
Default connection
| Field | Typical value |
|---|---|
| Port | 5055 |
| Scheme | http on LAN, https behind a reverse proxy |
| Auth | Account sign-in (session), or API key in the X-Api-Key header |
Add in Kochab
- Open More > Stacks & Services > + > Add service and choose Seerr.
- Enter your host and port (usually 5055), set Use HTTPS to match the address, and tap Next.
- On Credentials, tap Sign in and choose a method your server offers: email and password, Jellyfin, Emby, or Plex. Complete that sign-in. To use the global API key instead, choose Enter an API key instead and paste it.
- Tap Next, then Test & Add.
Requests and actions follow the connected account’s permissions. A household sign-in keeps that user’s permissions. A global API key gives administrator access. Kochab asks you to Sign in again when a session expires; restoring a backup does not restore that session.
TLS
See Certificate trust for self-signed certificates.