Updating node expiry dates in bulk

Request

To update the expiry dates on multiple nodes (and, optionally, the associated editorial contents), send a PATCH request to:

https://<host>:<port>/cpm/content/v1/nodes/bulkUpdateDates

Headers

• Content-Type: application/json

Mandatory arguments

All of the following arguments are part of the request body:

• nodeRefs – an array of node IDs

• You must specify at least one of start and end:

  • start – new start date in ISO 8601 format (GMT date/time up to the second : yyyy-mm-ddThh:mm:ssZ)

  • end – new end date in ISO 8601 format (GMT date/time up to the second : yyyy-mm-ddThh:mm:ssZ)

• updateContentDates – if true, both the node and editorial content validity dates are updated. If false, only the node validity dates are updated.

Other arguments

None

Example

{
  "updateContentDates": "true",
  "nodeRefs": [
    "A",
    "B",
    "C"
  ],
  "start": "2026-03-30T00:00:01Z",
  "end": "2027-03-30T00:00:01Z"
}

Response

A successful request returns an HTTP 200 status.

A bad request returns an HTTP 400 status.

See also

Content and Product Manager (CPM) API documentation: content v1