Torznab & RSS
To access the Torznab API, you should instead specify your API key as the apikey query parameter.
The Torznab API is only meant to be used by automation software, such as Sonarr or Radarr. If you want more rich data, use the JSON API instead.
The base URL for the Torznab API is https://nekobt.to/api/torznab
Rate Limiting
Search requests are rate limited per user, or per IP address when no apikey is supplied. Capabilities (t=caps) is not rate limited. As with the JSON API, the exact limits are not publicly shared.
If you exceed the limit you will receive a 429 Too Many Requests plain-text response. Use the Retry-After header to determine how long to wait before retrying.
HTTP/2 429
retry-after: 37
content-type: text/plain
rate limit exceeded, slow down your polling interval
The limit is set well above what normal automation needs. A typical RSS sync uses only a handful of requests per hour. If you are hitting it, your polling interval is too low. Sonarr, Radarr and Prowlarr all honour Retry-After and will back off on their own.
Get Torznab Capabilities
GET
/api?t=caps
Returns the capabilities of the Torznab API, such as supported search types and metadata formats.
Search Torrents (RSS Feed)
GET
/api?t=search
Searches for torrents. The following query parameters are supported:
italics = default, ? = optional
By default, the Torznab API provides magnet links rather than torrent files, so that torrent clients use the auto title and not the torrent title (important for tag matching). Only use link=torrent if your setup needs torrent files.
With link=torrent and an apikey, each download link contains your API key. Don't share the feed output.