Skip to main content

Install a package

POST 

/package_installations

Install a package at an NRN. The installation sets where in your organization the package's specification can be used (visible_to) and which revision new services and scopes are created with (default_revision_id). Nothing is copied: the specification, its actions and its links stay the publisher's.

You can install a global package or one your organization owns, and you need read access to the package.

When you omit default_revision_id, the package's default revision is resolved at that moment and stored. If the package has no default, its latest revision is used. The installation stays on that revision until you move it: a new release of the package doesn't change it.

ℹ️ Note: The request fails with 400 when the package belongs to another organization and isn't global, when the revision is deprecated or belongs to another package, or when a visible_to entry is outside your organization. It fails with 409 when the package is already installed at that NRN.

Request​

Responses​

The installation.