API Endpoints & Methods

ProGet provides a variety of API methods and endpoints to upload/download packages, manage feeds, audit package compliance, assess vulnerabilities, etc.

The easiest way to work with the ProGet API is by using pgutil a cross-platform Command-line Interface (CLI) tool. You can also use HTTP Endpoints and the .NET library (NuGet package) that pgutil uses under-the-hood.

pgutil Command-line Interface

pgutil is an open-source (github.com), cross-platform command line tool that's easy to download and install.

dotnet tool install pgscan

Once you've installed pgutil, you can simply type pgutil help to get a list of all of the commands and options available. You can also register sources so that you don't always have to specify urls, feeds, and API keys, etc.

pgutil packages upload --source=corpx-dev --input-file=Newtonsoft.Json.13.0.3.nupkg

See the Getting Started with pgutil guide to learn more.

HTTP Endpoints

API for Third-party Packages and Feed Types

To support third-party package formats such as NuGet, npm, etc., ProGet implements a number of third-party APIs. We provide only minimal documentation for these APIs, as they are usually either already documented elsewhere. However, you can usually find the basics by searching for specific things you want to do with the API, such as "how to search for packages using the NuGet API" or "how to publish an npm package using the API".

Native API

The ProGet Native API is a lower-level API that allows manipulation of most settings and data within ProGet outside the scope of third-party feeds. It should be avoided if another API is suitable, and is documented here: ProGet Native API Reference

.NET library (NuGet package