The document describes methods available in NZBGet version 13.0 and later. The document is updated after a new stable version is out. Current testing version may have methods or fields not described here; these methods or fields may change before getting stable.
NZBGet supports XML-RPC, JSON-RPC and JSON-P-RPC. RPC-protocols allow to control the program from other applications. Many programming languages have libraries, which make the usage of XML-RPC, JSON-RPC and JSON-P-RPC very simple. The implementations of all three protocols in NZBGet are equal: all methods are identical. You may choose the protocol, which is better supported by your programming language.
NZBGet has three pairs of username/password:
v15.0 Restricted user can control the program with few restrictions. He has access to web-interface and can see most program settings. He can not change program settings and can not view security related options or options provided by extension scripts. In terms of RPC-API the user:
v15.0 This user has only two permissions:
The RPC server uses HTTP basic authentication. The URL would be something like:
http://username:password@localhost:6789/xmlrpchttp://username:password@localhost:6789/jsonrpchttp://username:password@localhost:6789/jsonprpcIf HTTP basic authentication is somewhat problematic the username/password can also be passed in the URL as the first part of the path:
http://localhost:6789/username:password/xmlrpcSecurity warning: HTTP authentication is not secure. Although the password is encoded using Base64 it is not encrypted. For secure communication use HTTPS (needs to be explicitly enabled in NZBGet settings by user).