Skip to content

Downloads & monitoring (admin)

HTTP routes and behavior for downloads & monitoring (admin).

GET /api/downloads/{instanceID}/queue # unified SABnzbd/qBittorrent/NZBGet/Transmission/Deluge/ruTorrent
POST /api/downloads/{instanceID}/pause|resume # whole client
POST /api/downloads/{instanceID}/queue/{itemID}/pause|resume
DELETE /api/downloads/{instanceID}/queue/{itemID}?deleteData=bool
GET /api/downloads/{instanceID}/history?limit=50
GET /api/watch-history/{instanceID}/activity # current streams + bandwidth (Tautulli or Tracearr instance)
GET /api/watch-history/{instanceID}/history?limit=50
GET /api/watch-history/{instanceID}/stats?days=30
GET /api/tautulli/{instanceID}/activity|history|stats # alias of the three above, kept for apps that predate Tracearr

The watch-history routes serve both providers through one handler with one wire shape. Streams and history items carry media_type, server, and server_type (empty when the provider does not know them; Tautulli names no server because it only ever has one), and history and stats carry a coverage block (plays, since, until, truncated, note) saying what the answer was computed from, so an empty list reads as absence rather than blindness. Tracearr has no ranked-stats endpoint, so its stats are derived from paged history (since = now minus the window, at most 20 pages of 100 plays, every row one play as Tautulli’s total_plays counts) and cached per window for five minutes; the note says when the walk was capped and the counts are a floor.

View the maintained source for this page.