Sign in
Publishing

Add assets to a bundle

Adds assets to an existing bundle or creates a new bundle. Bundle resolution: (1) look up by bundleId, (2) if not found, look up unsent bundles by bundleName, (3) if still not found, auto-create a new bundle. A non-matching bundleId does NOT return 404 — it falls through to name lookup and then auto-creation. Assets already in the bundle are silently skipped (idempotent). Individual asset failures (e.g., no publish permission) are reported in the errors list as human-readable strings, not as HTTP errors.

post/api/v1/bundles/assets

Request body

bundleIdstring

Optional bundle ID. If provided and found, assets are added to this bundle. If not found, falls through to bundleName lookup, then auto-creation — does NOT return 404

bundleNamestring

Optional bundle name. Used as fallback when bundleId is not provided or not found. Searches unsent bundles by name (case-insensitive). If no match, a new bundle is created with this name

assetIdsstring[] required

List of asset identifiers to add to the bundle

Example request

{
  "bundleId": "550e8400-e29b-41d4-a716-446655440000",
  "bundleName": "My Content Bundle",
  "assetIds": [
    "asset-123",
    "asset-456"
  ]
}

Response

Assets processed (check errors list for per-asset failures)

i18nMessagesMapobject
permissionsstring[]

Example response

{
  "entity": {
    "bundleId": "550e8400-e29b-41d4-a716-446655440000",
    "bundleName": "My Content Bundle",
    "total": 5
  }
}

Changes

No recorded changes to this endpoint across all 1 revision of this API.