qBittorrent Shim and Automation

🇬🇧 English · 🇫🇷 Français

qBittorrent Shim & Automation

Hydra exposes a qBittorrent v4 WebUI-compatible API under /api/v2/* so the usual automation stack talks to it unchanged: autobrr, Sonarr / Radarr / Lidarr, cross-seed, etc.

Pointing tools at Hydra

Configure the tool's "qBittorrent" download client with:

• Host / port → your Hydra host, port 8199.
• Category → drives placement and save-path (Categories and Routing).

The shim does not check the native API key. /api/v2/* uses qBittorrent's own cookie login (it always succeeds); the X-Api-Key guard is only on the native /api/*. Don't expose 8199 to the internet unprotected.

Supported operations

Add, list (torrents/info), properties, files, trackers, pause/resume, delete, categories, and recheck. Two add-time behaviours worth knowing:

• skip_checking=true → seed data already on disk without re-hashing (trust-fast). The cross-seed / hardlink path.
• POST /api/v2/torrents/recheck (with hashes=<infohash>) → force a hash-check of on-disk data. Hoard engine only; hashes=all is ignored on purpose (no mass-recheck storms). See Adding Torrents and Existing Data.

cross-seed

cross-seed injects matches via the qBit API with skip_checking=true and an explicit save-path pointing at your existing data. That's the intended trust-fast path — Hydra starts seeding the linked data immediately. If you'd rather have it verified, drop skip_checking and let the recheck run.

autobrr

autobrr filters push new releases to the qBit client with a category; Hydra routes them per that category. Nothing Hydra-specific to configure beyond the category setup.