Using the RPC interface
The MPR RPC provides a simple way to interact with the MPR in a way that applications and automated systems can easily use. Requests are sent via HTTP GET requests, and the MPR sends back a JSON response.
All requests for the RPC interface are sent to
https://mpr.hunterwittenborn.com/rpc/, followed by various query parameters to describe the request.
Query parameters use
? for the first query argument, followed by
& to separate any further arguments.
Two query types are currently supported:
Instructions for using each are as follows:
search is used to perform various types of searches against the MPR.
Arguments for searches are constructed as follows:
The value for
v should currently always be set to five. New features may be introduced into the RPC interface in the future, in which case the version will be required to be bumped to utilize the new features.
Do not use older versions of the API under any circumstance. They will be completely removed in the future, with no remediation for users who are currently using them.
The value for
by can be set to any of the following:
name(search via package names)
name-desc(search via package names and descriptions)
maintainer(search via package maintainer names)
depends(search for packages that contain
optdepends(search for packages that contain
makedepends(search for packages that contain
checkdepends(search for packages that contain
by argument will default to doing searches against
The value of
arg should be set to the string to look up against the relevant value under
by. Only one argument should be provided for
arg, and providing multiple will cause the lookup to default to the last
arg parameter provided.
info is used to pull information on specific packages.
To construct an
info request, use the following:
See using-the-rpc-interface/#search for information on how to use the
arg accepts the name of any package on the MPR. Any number of packages may be provided, with each being specific via a separate
arg parameter like so: