Release notes

July 2026

Renamed and moved in knowledge base

To be more consistent with the functionality of the corresponding Mediagenix Hive application, the Publication sheet API has been renamed to Title management API. It has also had a number extensions and changes.

Requests to create and update content

What changed

    New publication sheet endpoints are available: POST /publication-sheets/{sigmaId}, PUT /publication-sheets/{sigmaId}, and GET /products/{sigmaId}/publication-sheets.

    The legacy create, retrieve and update publication sheet endpoints remain available but are marked as deprecated.

    Content creation and partial update endpoints are now exposed through POST /products and PATCH /products/{programSigmaId}.

    The product detail response for GET /products/{sigmaId} now returns richer JSON reference objects for many dropdown/reference fields instead of raw UUID strings.

    The product detail response also exposes additional metadata fields, including sports, press, content collection, and audit-related fields.

Why this matters

    Integrators can use stable, clearer publication sheet URLs under /publication-sheets.

    Consumers of product detail responses can now display richer reference information without resolving every dropdown UUID separately.

    Existing integrations using legacy publication sheet endpoints should plan migration because those endpoints are now deprecated.

    Clients that deserialize GET /products/{sigmaId} into strict models must update those models because several fields changed from UUID strings to objects.

Affected endpoints

Added

Publication sheets

    POST /publication-sheets/{sigmaId}

    PUT /publication-sheets/{sigmaId}

    GET /products/{sigmaId}/publication-sheets

Content

    POST /products

    PATCH /products/{programSigmaId}

Deprecated

    POST /contents/{sigmaId}/publicationDetails

    PUT /contents/publicationDetails/{pubId}

    GET /contents/{sigmaId}/publicationDetails

Updated

    GET /products/{sigmaId}

New attributes

    Product detail responses now include additional metadata for press handling, content collections, sports information, availability, and audit details.

    New top-level product detail attributes include isAvailable, hasImage, pressStatus, pressStatusDate, dateCreated, responsible, contentCollectionName, contentCollectionOrderNumber, sportEventTitle, leagueTitle, homeTeam, and awayTeam.

API details

    The new specification is titled Title management API.

    No security requirements were added or removed in the compared path operations.

    The legacy endpoint path variables were normalised in the new file, for example {contentId} is now represented as {sigmaId}.

New fields

    GET /products/{sigmaId} adds top-level response fields such as additionalDescription1, additionalDescription2, additionalDescription3, awayTeam, homeTeam, contentCollectionDisplayNumber, contentCollectionName, contentCollectionOrderNumber, dateCreated, distributorReference, externalReference, hasHistoricReruns, hasImage, hideEpisodeNrsForPress, isAvailable, pressStatus, pressStatusDate, responsible, seasonTitle, shortDescriptionTTV, shortSummaryPress, sportEventTitle, leagueTitle, studio, and userCreatedIdentification.

    WOnProgramPressInformationRecordRequest.tenantSpecificAttributes is available on the new publication sheet create/update endpoints.

Breaking changes

Breaking changes were detected.

    GET /products/{sigmaId}: many reference fields changed from raw UUID strings to objects, usually with an id property. This is breaking for clients with strict response DTOs or JSON schema validation.

    PUT /contents/publicationDetails/{pubId} and POST /contents/{sigmaId}/publicationDetails: cascadedInformation was removed from the response model. This is breaking for clients reading cascaded publication sheet values from these legacy endpoints.

    POST /contents/{sigmaId}/publicationDetails , PUT /contents/publicationDetails/{pubId} and GET /contents/{sigmaId}/publicationDetails are now deprecated. Deprecation is not a runtime breaking change, but it is migration-relevant.

YAML changes

Paths added
  • POST /publication-sheets/{sigmaId}
  • PUT /publication-sheets/{sigmaId}
  • GET /products/{sigmaId}/publication-sheets
  • POST /products
  • PATCH /products/{programSigmaId}
Paths removed

None.

Paths updated
  • GET /products/{sigmaId}
  • POST /contents/{sigmaId}/publicationDetails
  • PUT /contents/publicationDetails/{pubId}

  • GET /contents/{sigmaId}/publicationDetails

Schemas added
  • WOnProgramPressInformationRecordRequest
  • WOnProgramPressInformationRecordResponseJson
  • PartialUpdateProductRequest
  • PSIProgramResponseJson
  • PSIProductTitleResponseJson
  • PSIFirmResponseJson
  • PSIPersonResponseJson
  • PSIUserIdentificationResponse
  • Title
Schemas removed

    CascadedInformationJson from the exposed legacy publication sheet response model.

    ConstraintValidationErrorInfo and Violation from exposed error responses.

Schemas updated

    PublicationDetailJson: Removed cascadedInformation.

    PSIProgramResponse / PSIProgramResponseJson: Added product, press, sport, audit, and content collection fields. Changed many dropdown/reference fields from UUID strings to objects.

    CreateContentJsonObject: Updated create contract and required fields for the new POST /products endpoint.

Consult the API Explorer for more details.

June 2026

Moved in BAPI KB structure

Since this API is mostly used for managing publication sheets, the Content API for publication sheets was renamed to Publication sheet API.

May 2026

Product search extended

Business impact

The product search functionality in the Content API for publication sheets has been extended.

What changed

  • Added new filters to the GET /products search endpoint

  • Enriched several fields in the product search response

  • Removed the version and fuzziness query parameters

  • Breaking change: Yes

New filters

The following query parameters were added to GET /products:

  • productCode: Filter based on product code

  • genre: Filter based on genre

  • createdOnStartDate: Filter based on creation date, start of range

  • createdOnEndDate: Filter based on creation date, end of range

  • copyrightSheetFilter: Filter based on whether copyright sheets are linked

  • copyrightSheetStatus: Filter based on copyright sheet status

  • copyrightSheetVersion: Filter based on copyright sheet version

  • seasonYear: Filter based on season year

  • productionFormRequestFilter: Filter based on production form request availability

Affected endpoints

Product search

  • GET /products

Example

Example request:

GET /products?productCode=OB00009376/__/0001&copyrightSheetFilter=true&seasonYear=2025

Updated response information

The product search response now contains additional information:

  • boGenres: Genres linked to the product

  • copyrightSheets: Copyright sheets linked to the product

  • hasActiveProductionForms: Indicates whether active production forms exist

  • subtitled: Indicate: whether the product is subtitled

  • timeSlotCategory: Time slot category of the product

Several existing fields now return richer objects instead of only identifiers, including:

  • source type

  • status

  • original language

  • category

  • department

  • product display type

  • content collection intentions

  • tags

  • production companies

  • contact person

  • season

  • series

Breaking changes

Yes. This change may be breaking because:

  • The version query parameter was removed

  • The fuzziness query parameter was removed

  • Several response fields changed from simple UUID strings to objects

  • boGenres and hasActiveProductionForms were added as required fields in the ProductSearchLightJson response schema

API details
Added query parameters on GET /products
  • productCode
  • genre
  • createdOnStartDate
  • createdOnEndDate
  • copyrightSheetFilter
  • copyrightSheetStatus
  • copyrightSheetVersion
  • seasonYear
  • productionFormRequestFilter
Removed query parameters on GET /products
  • version
  • fuzziness
Updated response schema: ProductSearchLightJson

Added properties:

  • boGenres
  • copyrightSheets
  • hasActiveProductionForms
  • subtitled
  • timeSlotCategory

Updated properties:

All changed from referencing UUID string to DropDownJson

  • sourceType
  • status
  • originalLanguage
  • categoryDropdown
  • department
  • productDisplayType
  • contentCollectionIntentions
  • tags
  • productionCompanies
  • contactPerson
  • season
  • series
YAML changes
Paths

Updated:

  • /products

No new paths were added.

Schemas

New:

  • ReferenceJson

Updated:

  • ProductSearchLightJson

  • SearchContentPublicationDetailJson

Comparison

YAMLs can be compared in more detail using: TextCompare

See the changes in the Explorer.

October 2024

Addition of Content API for publication sheets

From this version on, it is possible to manage publication sheets using part of the content API. It allows to

  • create, retrieve, delete and update publication sheets;

  • search for and get details of content.

For more information, see the OpenAPI definition.