Release notes

May 2026

Separate endpoints for publication period

Business impact

Publication period management in the Content Budgeting API was redesigned and decoupled from projects.

Customers can now manage publication periods directly through dedicated endpoints and search publication periods independently from projects. This improves integrations with planning and budgeting workflows and simplifies publication period management across projects.

What changed

    Added standalone publication period endpoints

    Added publication period search functionality

    Updated publication period request and response structures

    Simplified error handling responses

    Removed projectId from publication period paths

    Breaking change: Yes

New attributes

  • project:
    Reference object linking a publication period to a project.

Affected endpoints

Publication periods

    GET /content-budgeting/publication-periods

    POST /content-budgeting/publication-periods

    GET /content-budgeting/publication-periods/{publicationPeriodId}

    PUT /content-budgeting/publication-periods/{publicationPeriodId}

    DELETE /content-budgeting/publication-periods/{publicationPeriodId}

Removed endpoints

    GET /content-budgeting/projects/{projectId}/publication-periods

    POST /content-budgeting/projects/{projectId}/publication-periods

    GET /content-budgeting/projects/{projectId}/publication-periods/{publicationPeriodId}

    PUT /content-budgeting/projects/{projectId}/publication-periods/{publicationPeriodId}

    DELETE /content-budgeting/projects/{projectId}/publication-periods/{publicationPeriodId}

Examples

Example request body of POST /content-budgeting/publication-periods:

{
			"project": {
			"id": "31d6cf76-cbc9-4e97-83db-3e6ff30180a7"
			},
			"startDate": "2025-03-30",
			"endDate": "2026-03-30"
		}

Example response of GET /content-budgeting/publication-periods/{publicationPeriodId}:

{
			"id": "31d6cf76-cbc9-4e97-83db-3e6ff30180a7",
			"project": {
			"id": "31d6cf76-cbc9-4e97-83db-3e6ff30180a7"
			},
			"startDate": "2025-03-30",
			"endDate": "2026-03-30"
		}

API details

New endpoints

    GET /content-budgeting/publication-periods

    POST /content-budgeting/publication-periods

    GET /content-budgeting/publication-periods/{publicationPeriodId}

    PUT /content-budgeting/publication-periods/{publicationPeriodId}

    DELETE /content-budgeting/publication-periods/{publicationPeriodId}

Breaking changes

    Publication period endpoints no longer contain projectId in the path

    Publication period request schemas now use a project reference object instead of a projectId path parameter

    Publication period response schemas changed from PublicationPeriodResponseJson to PublicationPeriodWithProjectResponseJson

    Error handling changed from ConstraintValidationErrorInfo to ErrorJson

New schemas

    PublicationPeriodWithProjectRequestJson

    PublicationPeriodWithProjectResponseJson

    ProjectReferenceJson

    ErrorJson

    BudgetLineProject

Removed schemas

    PublicationPeriodRequestJson

    PublicationPeriodResponseJson

    ConstraintValidationErrorInfo

    ConstraintViolationObject

    ConstraintDescriptorObject

    Violation

    Path

YAML changes

Paths added

    /content-budgeting/publication-periods

    /content-budgeting/publication-periods/{publicationPeriodId}

Paths removed

    /content-budgeting/projects/{projectId}/publication-periods

    /content-budgeting/projects/{projectId}/publication-periods/{publicationPeriodId}

Updated schemas

ProjectRequestJson
Examples updated to use object references for dropdown values.

ProjectResponseJson
Examples updated to use object references for dropdown values.

BudgetLineSearchResponseJson
Project schema changed from Project to BudgetLineProject.

Access

Latest YAML available via: GET /api

Comparison

YAMLs can be compared in more detail using: TextCompare

See the changes in the Explorer.

March 2026

New version of content budgeting API

The structure of the content budgeting API YAML has been improved but there are no functional changes. The latest version can be seen in the Explorer.

December 2025

External references added to projects and publication periods

In this version, the externalReference attribute was added to the calls and responses for projects and publication periods.

Additionally, in the YAML, description and example attributes were added to the path parameter IDs of projects, publication periods and budgets lines, as well as the 412 error code with description "Precondition Failed".

These changes can be seen in the Explorer.

September 2025

Addition of Content Budgeting API

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

  • projects;

  • publication periods;

  • budget splits;

  • budget lines;

  • content batches;

  • amortizations.

For more information, see the OpenAPI definition.