This page explains the different feed endpoints available on MyGet. Depending on the client you are using (NuGet.exe, Orchard CMS, npm, ...), these endpoints can be configured as the package source or as the publish endpoint.
Feed endpoints that can be used
Various endpoints are available for MyGet feeds.
NuGet-compatible feed endpoints
MyGet has the following feed endpoints available for NuGet:
- /F/<your-feed-name>/api/v3/index.json - the NuGet v3 API endpoint
- /F/<your-feed-name>/api/v2 - the NuGet v2 API endpoint for consuming packages
- /F/<your-feed-name>/api/v2/package - the NuGet v2 API endpoint for pushing packages
- /F/<your-feed-name>/api/v1 - the NuGet v1 API endpoint for consuming and pushing packages (still in use by Orchard CMS and some others)
The following table lists which endpoint can be used with which client:
|Endpoint||NuGet < v1.6
|NuGet > v1.6
|NuGet > v3.0
|NuGet Package Explorer||Orchard CMS||Chocolatey / OneGet||Web browser|
|/F/<your-feed-name>/api/v1||yes||yes (no push)||yes||yes||yes||yes||yes|
Symbol server endpoints
MyGet has the following endpoints available for symbol server (debugging in Visual Studio and WinDbg):
- /F/<your-feed-name>/api/v2/package - the symbols package publish endpoint
- /F/<your-feed-name>/symbols - the symbol server endpoint
Npm-compatible feed endpoints
MyGet has the following feed endpoints available for npm:
- /F/<your-feed-name>/npm - the npm API endpoint
Bower-compatible feed endpoints
MyGet has the following feed endpoints available for Bower:
- /F/<your-feed-name>/bower - the Bower API endpoint
Vsix-compatible feed endpoints
MyGet has the following feed endpoints available for Vsix (Visual Studio extensions):
- /F/<your-feed-name>/vsix - the VSIX Atom feed API endpoint
- /F/<your-feed-name>/vsix/package - the VSIX upload endpoint
Private feed endpoints and authentication
When accessing private feeds, these endpoints all require basic authentication. If the client that is being used does not support basic authentication, a pre-authenticated feed URL can be used. The pre-authenticated feed URL is available from the feed's feed details page.
Warning! As pre-authenticated feed URLs contain sensitive information, it is recommended to never use pre-authenticated feed URLs unless absolutely needed. Sharing the pre-authenticated feed URL can potentially give others read and write access to the feed!
Since pre-authenticated feed URLs contain your API key in the URL, we advise to use a separate access token generated specifically for the purpose of using a pre-authenticated feed endpoint so that it can be revoked at any time.