Updating content expiry dates in bulk

Request

To update the expiry dates on multiple editorial contents, send a PATCH request to:

https://<host>:<port>/metadata/content/v1/editorialContents/bulkUpdateDates

Headers

• Content-Type: application/json

Mandatory arguments

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

• editorialRefs – an array of editorial content IDs

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

Optional arguments

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

Example

{
    "editorialRefs": [
        "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