API reference
Content packs
4 operations in this area of the contract. Every one declares the permission it requires.
Contract version 0.2.0All areas
Operations
GET
/v1/content-packsImported content packs
Required permission: contentpack.pack.readlistContentPacks
Show parameters and responsesHide parameters and responses
Responses
200Content packsContentPackPage
GET
/v1/content-packs/{packID}/diffPreview what applying a pack would change
Required permission: contentpack.pack.readdiffContentPack
Required by architectural mandate 5. `conflicts_with_overrides` counts the changes that need a human decision: a pack default moving underneath a customisation the tenant made deliberately. The override still wins, but the compliance officer needs to know the ground shifted beneath it.
Show parameters and responsesHide parameters and responses
Parameters
| Name | In | Type | Description |
|---|---|---|---|
packIDrequired | path | string | — |
Responses
200Upgrade diffPackDiff404—
POST
/v1/content-packs/{packID}/installPropose applying a content pack
Required permission: contentpack.pack.installinstallContentPack
Applying regulatory content is a four-eyes action. The diff is what gets approved, and the approved diff is retained on the installation record so the decision is reconstructable.
Show parameters and responsesHide parameters and responses
Parameters
| Name | In | Type | Description |
|---|---|---|---|
packIDrequired | path | string | — |
Responses
202Installation proposed and awaiting approvalApprovalRequest400The pack failed signature or digest verification
GET
/v1/content-packs/installationsThis tenant's pack installation history
Required permission: contentpack.pack.readlistPackInstallations
Show parameters and responsesHide parameters and responses
Responses
200Installations, newest firstPackInstallationPage