qbittorrent

Automating qBittorrent torrent management via the WebUI API requires scripts that authenticate with your running WebUI instance using credentials stored in the environment. This approach allows you to list, add, pause, resume, and delete torrents programmatically across multiple downloads.

Adding torrents and managing speed limits using the qBittorrent API is fully supported. You can add torrents by magnet link, URL, or file, and programmatically adjust speed limits across active downloads to prioritize network traffic.

Running qBittorrent API scripts for download automation requires a running qBittorrent WebUI instance. You must also configure your WebUI credentials in the environment variables so the scripts can authenticate and execute commands.

Organizing torrents by category and tags through the qBittorrent WebUI involves calling specific API endpoints via scripts. This centralizes routine torrent operations, enabling you to filter lists and automatically categorize new downloads.

Listing and filtering active torrents in qBittorrent is best handled by automating API calls through the WebUI. This method retrieves current download statuses dynamically, allowing you to apply filters based on categories and tags.

If your qBittorrent API script fails to authenticate with the WebUI, it typically means the required credentials are missing or incorrect in your environment variables. The WebUI must be actively running and accessible for scripts to connect successfully.