-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
API Key Authentication (≥v5.2.0)
Note
API key authentication is available starting from qBittorrent v5.2.0 or WebAPI v2.14.1
You can authenticate to the qBittorrent WebAPI using an API key. This allows for stateless authentication without the use of cookies.
Currently, only a single API key is supported. This key can be rotated, which will immediately invalidate the previous key.
API keys are 32 characters long. They start with the prefix qbt_
followed by 28 random alphanumeric characters. Each key is generated with 160 bits of entropy.
Specify the key in the Authorization
header using a scheme of Bearer
. For example: Authorization: Bearer <API_KEY>
.
To generate an API key:
- Open qBittorrent Preferences
- Click on WebUI
- Navigate to the API Key section
- Click on the Generate icon.
API keys cannot be used to fetch the WebUI or other static assets. They also cannot interact with the WebAPI's auth
endpoints, including login
and logout
.
- Installing qBittorrent
- Frequently Asked Questions (FAQ)
- qBittorrent options (current and deprecated)
- How to use qBittorrent as a tracker
- How to use portable mode
- Anonymous mode
- How to bind your vpn to prevent ip leaks
State | Version |
---|---|
Current | qBittorrent >= 5.0 |
Previous | qBittorrent v4.1.0 - v4.6.x |
Previous | qBittorrent v3.2.0 - v4.0.x |
Obsolete | qBittorrent < v3.2.0 |
- Let's Encrypt Certificates + Caddy2 Reverse Proxy
- Let's Encrypt certificates + NGINX reverse proxy - Linux
- Let's Encrypt certificates - Linux
- Self-signed SSL certificates - Linux
- Running qBittorrent without X server (WebUI only)
- Running qBittorrent without X server (WebUI only, systemd service set up, Ubuntu 15.04 or newer)
- OpenVPN and qBittorrent without X server
- Coding style
- Contributing
- How to write a search plugin
- Using VSCode for qBittorrent development
- Setup GDB with Qt pretty printers
- How to debug WebUI code