Release notes

May 2026

Additional functionality in Content Strategy API

The Strategic planning API was renamed to Content strategy API.

The API has been extended with additional release window management functionality and improvements to error handling.

Customers can now:

manage MOD (Mediagenix On Demand) states for release windows

work with multiple release window periods

retrieve release window content batch link information

receive simplified and more consistent API error responses

These changes improve integrations with operational planning workflows and downstream delivery processes.

What changed

Added MOD state management for release windows

Added support for multiple release window periods

Added endpoint to retrieve release window content batch links

Simplified and standardized error responses

Deprecated the channel attribute in favor of channels

Breaking change: Yes

New attributes

• releaseWindowPeriods:
  List of release window periods linked to a release window.

• modState:
  Indicates the MOD status of a release window.

• releaseWindowContentBatchLinkId:
  Identifier of the release window content batch link.

Affected endpoints

Release windows

GET /plans/{planId}/release-windows

POST /plans/{planId}/release-windows

PUT /plans/{planId}/release-windows/{releaseWindowId}

GET /plans/{planId}/release-windows/{releaseWindowId}

New endpoints

PUT /plans/{planId}/release-windows/{releaseWindowId}/mod-state

GET /release-window-content-batch-links/{releaseWindowContentBatchLinkId}

Examples

Example request for PUT /plans/{planId}/release-windows/{releaseWindowId}/mod-state:

{
				"status": "SUCCESS",
				"message": "Successfully delivered to MOD"
		}

Example response of GET /plans/{planId}/release-windows/{releaseWindowId}:

{
				"id": "31d6cf76-cbc9-4e97-83db-3e6ff30180a7",
				"title": "My release window",
				"releaseWindowPeriods": [
				{
				"startDate": "2025-10-21",
				"endDate": "2025-10-25"
				}
				],
				"modState": {
				"status": "SUCCESS",
				"message": "Successfully delivered to MOD"
				}
		}

For developers

API details

New endpoints

• PUT /plans/{planId}/release-windows/{releaseWindowId}/mod-state:
  Set the MOD state of a release window.

• GET /release-window-content-batch-links/{releaseWindowContentBatchLinkId}:
  Retrieve release window content batch link details.

New fields

releaseWindowPeriods
Type: array
Contains multiple release window periods.

modState
Type: object
Contains MOD delivery status information.

releaseWindowContentBatchLinkId
Type: string (UUID)

Updated fields

channel
Deprecated: true
Please use channels instead.

Error handling changes

Error responses were standardized using the new ErrorJson schema.

Previous validation-specific schemas were removed and replaced by a simplified structure:

{
				"message": "Error message"
		}

YAML changes

Paths added

• /plans/{planId}/release-windows/{releaseWindowId}/mod-state
• /release-window-content-batch-links/{releaseWindowContentBatchLinkId}

Paths updated

• /plans/{planId}/release-windows
• /plans/{planId}/release-windows/{releaseWindowId}

New schemas

• ErrorJson
• MODStateRequestJson
• MODStateResponseJson
• ReleaseWindowPeriodRequestJson
• ReleaseWindowPeriodResponseJson
• ReleaseWindowContentBatchLinkResponseJson
• Plan

Updated schemas

ReleaseWindowRequestJson

Added:

• releaseWindowPeriods

Deprecated:

• channel

Removed:

• startDate
• endDate
• endDateFormula

ReleaseWindowResponseJson

Added:

• releaseWindowPeriods
• modState

Deprecated:

• channel

FormulaRequestJson

Required fields updated:

• offset is now required

FormulaResponseJson

Required fields updated:

• offset is now required

ContentBatchResponseJson

Updated:

• productDuration changed from object to string

Error handling schemas

Removed:

• ConstraintValidationErrorInfo
• ConstraintViolationObject
• ConstraintDescriptorObject
• Violation
• Path

Added:

• ErrorJson

Access

Latest YAML available via: GET /api

Comparison

YAMLs can be compared in more detail using: TextCompare

March 2026

Events added to strategic planning API

Previously, the API already provided endpoints for plans, release windows and content batches.

From this version, events have also been added to the API. They represent important moments of a timeline, such as public holidays, content launches, competitor events and generic events.

The following calls were added:

• GET /event/{eventId}:
  Get all the details of an event.

• GET /events:
  Search for events.

• GET /events/list:
  List events using criteria.

• POST /events:
  Create events.

• PUT /event/{eventId}:
  Update an event.

• DELETE /event/{eventId}:
  Delete an event

These changes can be seen in the Explorer.

December 2025

External references added to plans and release windows

From this version, the externalReference attribute has been added to the calls for plans and release windows.

These changes can be seen in the Explorer.

November 2025

Addition of Strategic Planning API

From this version on, it is possible to manage strategic planning using the API. It allows to manage

• plans;

• release windows;

• content batches.

For more information, see the OpenAPI definition.