qBittorrent WebUI API reference covering authentication, sync, transfer, torrent, RSS, and search endpoints for qBittorrent 5.0+.
60
68%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.github/skills/qbittorrent-api/SKILL.mdUse this skill when you need to integrate with qBittorrent's WebUI API.
/api/v2GET; mutations use POST405 Method Not Allowed on modern servers/api/v2/auth/loginqBittorrent uses cookie-based auth.
POST /api/v2/auth/login
username, password200 and sets SID cookie403POST /api/v2/auth/logoutSend Referer or Origin matching the request host/port.
| Group | Base | Notes |
|---|---|---|
| Auth | /api/v2/auth/* | Login/logout |
| Application | /api/v2/app/* | Version, preferences, cookies, save path |
| Log | /api/v2/log/* | Main log and peer log |
| Sync | /api/v2/sync/* | Incremental state updates |
| Transfer | /api/v2/transfer/* | Global rates and limits |
| Torrents | /api/v2/torrents/* | List, inspect, mutate, files, categories, tags |
| RSS | /api/v2/rss/* | Feed and rule management |
| Search | /api/v2/search/* | Search jobs and plugins |
GET /app/versionGET /app/webapiVersionGET /app/buildInfoGET /app/preferencesPOST /app/setPreferences
json={...}GET /app/defaultSavePathGET /app/cookiesPOST /app/setCookiesGET /sync/maindata?rid=<rid>
rid, full_update, torrents, torrents_removed, categories, categories_removed, tags, tags_removed, server_stateGET /sync/torrentPeers?hash=<hash>&rid=<rid>Use sync/maindata for efficient polling instead of repeatedly calling full torrent list endpoints.
GET /transfer/infoGET /transfer/speedLimitsModePOST /transfer/toggleSpeedLimitsModeGET /transfer/downloadLimitPOST /transfer/setDownloadLimit
limit bytes/secGET /transfer/uploadLimitPOST /transfer/setUploadLimit
limit bytes/secPOST /transfer/banPeers
peers=host:port|host:portGET /torrents/info
filter, category, tag, sort, reverse, limit, offset, hashesGET /torrents/properties?hash=<hash>GET /torrents/trackers?hash=<hash>GET /torrents/webseeds?hash=<hash>GET /torrents/files?hash=<hash>GET /torrents/pieceStates?hash=<hash>GET /torrents/pieceHashes?hash=<hash>Important torrents/info response fields include state, progress, rates, ETA, save path, category, tags, tracker, queue position, availability, and content sizes.
POST /torrents/pausePOST /torrents/resumePOST /torrents/delete
hashes, deleteFilesPOST /torrents/recheckPOST /torrents/reannouncePOST /torrents/add
urlstorrents (repeatable file part)savepath, category, tags, skip_checking, paused, root_folder, rename, upLimit, dlLimit, ratioLimit, seedingTimeLimit, autoTMM, sequentialDownload, firstLastPiecePrioPOST /torrents/addTrackersPOST /torrents/editTrackerPOST /torrents/removeTrackersPOST /torrents/addPeersPOST /torrents/increasePrioPOST /torrents/decreasePrioPOST /torrents/topPrioPOST /torrents/bottomPrioPOST /torrents/filePrio
hash, id, priorityindex from /torrents/files when availablePOST /torrents/downloadLimitPOST /torrents/setDownloadLimitPOST /torrents/setShareLimitsPOST /torrents/uploadLimitPOST /torrents/setUploadLimitPOST /torrents/setLocationPOST /torrents/renamePOST /torrents/setCategoryGET /torrents/categoriesPOST /torrents/createCategoryPOST /torrents/editCategoryPOST /torrents/removeCategoriesPOST /torrents/addTagsPOST /torrents/removeTagsGET /torrents/tagsPOST /torrents/createTagsPOST /torrents/deleteTagsPOST /torrents/setAutoManagementPOST /torrents/toggleSequentialDownloadPOST /torrents/toggleFirstLastPiecePrioPOST /torrents/setForceStartPOST /torrents/setSuperSeedingPOST /torrents/renameFilePOST /torrents/renameFolderRSS is under /api/v2/rss/* and search is under /api/v2/search/*.
Important endpoints:
addFolder, addFeed, removeItem, moveItem, items, markAsRead, refreshItem, rule CRUD, articlesstart, stop, status, results, delete, plugin list/install/uninstall/enable/update`Electorrent primarily depends on:
sync/maindatatorrents/addtorrents/files + torrents/filePrio89eb958
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.