Have a question? Want to report an issue? Contact JFrog support

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


title* Don't prefix the repository path with api/<pkg>, but watch out for exceptions

For some packaging formats, when using the corresponding client to access a repository through Artifactory, the repository key in the URL needs to be prefixed with api/<pkg> in the path. For example, in the case of Npm repositories, the repository key should be prefixed with api/npm. Nevertheless, there are exceptions to this rule. For example, when replicating PyPI Maven repositories, you do not need to add a prefix the remote repository path with api/pypi.

The considerations of whether to prefix the repository key with api/<pkg> or not are the same as those when configuring smart remote repositories. For a detailed list of package formats that should be prefixed with api/<pkg>, please refer to Configuration under Smart Remote Repositories.