Release notes

2025r3

Target group in content API

On a product, it is possible to define the target group related to the buying order. It was previously not available in the content API.

From this version, the targetGroup attribute has been added to the following calls:

• GET /products/{contentId}

• Program calls:

  • POST /programs

  • PUT /programs/{contentId}

  • GET /programs/{contentId}

  • POST/programs/{contentId}/versions/{versionId}

• Series calls:

  • POST /series

  • PUT /series/{contentId}

  • GET /series/{contentId}

• Season calls:

  • POST /seasons

  • PUT /seasons/{contentId}

  • GET /seasons/{contentId}

  • POST/seasons/{contentId}/versions/{versionId}

• Episode calls:

  • POST /episodes

  • PUT /episodes/{contentId}

  • GET /episodes/{contentId}

  • POST/episodes/{contentId}/versions/{versionId}

• Content collections:

  • POST /contentCollections

  • PUT /contentCollections/{contentId}

  • GET /contentCollections/{contentId}

An example of the GET /products call:

{
    "contentId": "1405730527",
    "contentType": "program",
    "title": "The Souvenir",
    "duration": "02:00:00",
    "productCode": "Kine6",
    "productionCompanies": [],
    "type": null,
    "status": null,
    "remarks": null,
    "pressSheets": [],
    "cast": [],
    "originalLanguage": null,
    "contentTargetGroup": null,
    ...
    "targetGroup": "A18-40",
    "masterVersionId": null,
    ...
}

A GET /targetGroups call was already available to get the values of the TargetGroup drop-down list.

API developers

The YAML has been updated for these changes. The latest version can be retrieved by using the GET /api call.

The following has changed:

At line 2917, the targetGroup property was added to the properties of the Content schema.
At line 3116, the targetGroup property was added to the properties of the ContentForGet schema.

For easier viewing, the YAMLs can also be compared here: TextCompare