Seerr Requests

Dashboard Status

This module is live for Overseerr or Jellyseerr-compatible APIs. The main dashboard shows request statistics only.

Primary API surfaces used for stats:

/api/v1/status
/api/v1/request?take=25&skip=0

The dashboard sends the API key in the x-api-key header.

Admin Fields

• Seerr URL
• API Key

Recommended Values

Seerr URL: https://requests.example.com
API Key: copied-api-key

Use the base URL, not a settings page URL and not /api/v1.

Overseerr: Find The API Key

1. Open Overseerr as an admin.
2. Go to Settings -> General.
3. Copy the API Key.
4. Confirm Application URL is set correctly if Overseerr is behind a reverse proxy.

Jellyseerr: Find The API Key

1. Open Jellyseerr as an admin.
2. Go to Settings -> General.
3. Copy the API Key.
4. If you set API_KEY as an environment variable, use that same value.

What The Dashboard Shows

• Pending, approved, available, declined, and total request counts from recent request data.
• Connection status and a short API note.

Search and request submission are intentionally not shown on the main dashboard.

Test From The Docker Host

Verify the key reaches Seerr with a safe GET endpoint first:

curl -fsSL \
  -H 'x-api-key: YOUR_API_KEY' \
  'https://requests.example.com/api/v1/status'

Verify request stats:

curl -fsSL \
  -H 'x-api-key: YOUR_API_KEY' \
  'https://requests.example.com/api/v1/request?take=25&skip=0'

Common Problems

• 401 or 403: wrong API key, regenerated key, or reverse proxy stripping headers.
• 404: the saved URL includes the wrong base path, or you included /api/v1 twice.
• Reverse proxy base paths: if Seerr runs under a subpath, include that subpath in Seerr URL.

Sources

• Overseerr settings docs: https://docs.overseerr.dev/using-overseerr/settings
• Jellyseerr general settings docs: https://docs.jellyseerr.dev/using-jellyseerr/settings/general