Your services

Seerr

Where Seerr’s API key comes from, why it has to be the owner’s, and which parts of Managerr a Seerr service brings with it.

Overseerr, Jellyseerr or Seerr

Seerr is the project that continues Overseerr and Jellyseerr, and Managerr speaks that version 1 API. Choose Seerr for an Overseerr or Jellyseerr installation that provides the compatible API. Test the connection; individual features can vary with the server version.

The stock port is 5055, and every request Managerr makes goes to api/v1 under the address you give it. If your server answers somewhere else — another port, a path prefix, a reverse proxy in front — give it that address instead. Add a service covers the address field.

The owner API key

The key lives in the Seerr server’s own Settings → General, and you have to be signed in as the owner to see it. The service editor says the same thing under the key field: for Seerr, use the owner’s API key.

Seerr’s API key is an administrator credential rather than a household login. Everything Managerr does through it is done as the owner, so anyone holding the phone can approve and decline. Treat the device accordingly.

Test Service checks the authenticated account endpoint and then server status. It does not separately validate every permission or action. Use the owner’s API key as requested by the service editor.

What it drives

Seerr drives the destination labelled Seerr, which opens on four views. Inbox is the request list, with Approve and Decline on a request you open. Issues lists what people reported through Seerr. Discover is for browsing something new. Tools reaches that server’s jobs, caches, logs and server information.

It also drives the Recommended shelf on Home, which asks Seerr for titles like the ones already watched. Home & Library covers that shelf; with a Tautulli service connected, its seeds come from real plays rather than from what your libraries monitor.

Connect more than one Seerr service and the Requests destination reads all of the enabled ones together. The bar at the top names the one you have narrowed to, or reads Seerr when you have not.

Artwork for Discover and for requests may load from the image provider Seerr names, which includes The Movie Database. That provider sees your device’s IP address and the image request, and never your API key. Privacy lists every place artwork can come from.

Destinations and profiles

Requesting something asks for a Server, a Resolution, a Quality profile and a Root folder — plus a Language profile where the server offers one, and Seasons to request for a series.

Every one of those lists comes from the Sonarr and Radarr services your Seerr server is configured with, including whether a 4K lane exists at all. Managerr reads them from Seerr and does not invent or override them. So if a profile you expected is missing, it is missing in Seerr: add it there and it appears here on the next load.

What a request status means

A request’s status and whether the media is actually on your server are two different things, and they are reported separately.

The inbox filter carries the first — Pending, Approved, Declined, Failed or Completed, with All for the lot. That is the state of the asking.

Availability is the second, and a title says it in its own words: Available to request, Requested, awaiting approval, Requested, Partly available or In your library. The two can disagree without either being wrong. Seerr tracks standard and 4K media separately. Managerr can show Requested and 4K Requested labels independently. Check the resolution when reviewing or creating a request; availability in one resolution does not mean the other is available.

For installation and server configuration, see Seerr documentation.