API always returns a list of packages. Package is a dictionary of the following format:

	"repo": "freebsd",
	"name": "firefox",
	"version": "50.1.0",
	"origversion": "50.1.0_4,1",
	"summary": "Widely used web browser",
	"categories": ["www"],
	"licenses": ["GPLv2+"],
	"maintainers": ["gecko@FreeBSD.org"],
	"www": ["http://www.mozilla.com/firefox"],
	"downloads": ["http://download.cdn.mozilla.net/pub/firefox/releases/50.1.0/source/firefox-50.1.0.source.tar.xz"]

Fields are:

name of repository for this package
name of subrepository (if applicable; for example, main or contrib or non-free for Debian)
package name as in repository
package version (sanitized)
package version as in repository (if different from version)
one-line description of the package
list of package categories
list of package licenses
list of package maintainers
list of package webpages
list of package downloads

Mandatory fields are repo, name and version, all other fields are optional.

Metapackage is a group of related packages from different repositories (though it may contain multiple packages from the same repository). Metapackage has its own name which is derived from package names. In most cases it's the same, but sometimes different package names are transformed into a single metapackage name to coalesce differently named packages from different repositories.

API allows to request packages for a single metapackage or for a range of metapackages.

Single metapackage

Get list of packages for specific metapackage (here, firefox):


Multiple metapackages

Following requests return data for multiple metapackages in form of metapackage name → list of packages dictionary. You may set a range of names to retrieve by specifying first or last name in range(inclusive or exclisive). API returns no more than 200 metapackages per request. By taking last (alphanumerically) name from a request and making another request with >name you can iterate through all metapackages. Empty output means end of data.

Get first 200 metapackages:


Get first 200 metapackages starting with firefox (inclusive):


Get first 200 metapackages after firefox (exclusive, e.g. firefox not included):


Get first 200 metapackages just before firefox (exclusive, e.g. firefox not included):


All metapackages requests support < and > syntax.

Filtered metapackages

Get metapackages present in specific repository (e.g. containing a package from that repository):


Get metapackages not present in specific repository:


Get metapackages outdated in specific repository:


Get metapackages for specific maintainer (e.g. containing a package with specific maintainer):


Get metapackages which are outdated for specific maintainer:



Get problems for specific repository or maintainer:

Output is an array of entries of the following format:
	"repo": "freebsd",
	"name": "abby",
	"effname": "abby",
	"maintainer": "ports@freebsd.org",
	"problem": "Homepage link \"https://code.google.com/archive/p/abby/\" points to Google Code which was discontinued. The link should be updated (probably along with download URLs). If this link is still alive, it may point to a new project homepage."

Fields are:

repository name
package name as in repository
repology metapackage name
package maintainer associated with the problem; may be null; note that if there are multiple package maintainers, problem is duplicated for each one
textual description of the problem