![]() This parameter must be named "callback" and must be passed first (before any other parameters). Each call to JSON-P-RPC has one additional parameter - the name of callback-function.Therefore parameter names are ignored but the order of parameters is important. Only positional parameters are supported in JSON-RPC.Multicalls are supported for XML-RPC and not supported for JSON-RPC.For secure communication use HTTPS (needs to be explicitly enabled in NZBGet settings by user). Although the password is encoded using Base64 it is not encrypted. Security warning: HTTP authentication is not secure. ![]() ![]() for XML-RPC: for JSON-RPC: for JSON-P-RPC: HTTP basic authentication is somewhat problematic the username/password can also be passed in the URL as the first part of the path:.The RPC server uses HTTP basic authentication with username and password from server's configuration file. You may choose the protocol, which is better supported by your programming language. The implementations of all three protocols in NZBGet are equal: all methods are identical. Many programming languages have libraries, which make the usage of XML-RPC, JSON-RPC and JSON-P-RPC very simple. RPC-protocols allow to control the program from other applications. NZBGet supports XML-RPC, JSON-RPC and JSON-P-RPC. If you need information for older NZBGet version please see a historical article RPC API reference 0.6.0-12.0. Current testing version may have methods or fields not described here these methods or fields may change before getting stable. The document is updated after a new stable version is out. The document describes methods available in NZBGet version 13.0 and later. About XML-RPC and JSON-RPC in NZBGet Status of this document
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |