Release notes

2025r10

Point in time custom attributes in business API

Custom attributes are supported in the content, copyright, MAM, on-demand schedule, person and trailer API.

Previously, the following types were available:

Boolean
Date
Decimal number
Drop-down list
Drop-down list for multiselection
Duration
Integer
Reference
String
Text
Web

From this version, custom attributes of the type Point in time can also be used in these APIs.

In the GET calls, such as GET /program, the following suffixes can be added to the call to either get only specified attributes in the response or all custom attributes of the supported types:

?customAttributes=attributeName,attributeName
?customAttributes=allCustomAttributes

For each custom attribute, the attribute name, value, and type will be given. The new type will be included in the response as follows:

...
    "customAttributes": [
        {
            "attributeName": "embargoTimestamp",
            "value": "2025-12-14T20:00:00Z",
            "type": "Point in time field"
        }
    ]
...

The Point in time custom attribute will be considered as a local timestamp in the Mediagenix Base platform in the default timezone, which is Brussels. When a GET call is done, the timestamp of the custom attribute is converted to UTC time.

For example, the Embargo timestamp from the example is 14/12/25 21:00:00. This is considered in the default timezone, Belgium, which is currently on UTC+1. When doing the GET call, the timestamp is returned as 2025-12-14T20:00:00Z.

In POST or PUT calls, an array of custom attributes needs to be provided with their attribute name and value. The new type should be specified as follows:

    "customAttributes": {
        "embargoTimestamp": "2025-12-14T20:00:00Z"
    }

The timestamp is converted from UTC to the default time zone before being saved in Mediagenix Base platform. This custom attribute type should follow the ISO 8601 format, meaning YYYY-MM-DDTHH:MM:SSZ.

For example, if 2025-12-14T20:00:00Z is sent, this will be saved as 21:00:00.

If the correct format is not used, the following error message is returned:

{
    "statusCode": "422",
    "message": "Operation cannot be completed due to violations",
    "timestamp": "2025-12-02T09:23:41Z",
    "concept": "Program",
    "id": "9502146329",
    "errors": [
        {
            "errorCode": "CORE-00002",
            "description": "Parsing error. Use ISO 8601 format",
            "data": [
                null
            ]
        }
    ]
}

API developers

The YAMLs will be updated in an upcoming version. Until then, the changes above can already be entered manually.

2023r9

Custom attributes in person API

Custom attributes were already supported in the content, MAM and trailer API.

From this version, the person API also supports custom attributes of the following types:

Boolean
Date
Decimal number
Drop-down list
Drop-down list for multiselection
Duration
Integer
Reference
String
Text
Web

In the GET /person call, the following suffixes can be added to the URL to either get only the specified attributes in the response or all custom attributes of the supported types:

?customAttributes=attributeName,attributeName
?customAttributes=allCustomAttributes

For example: GET /persons/1111882517?customAttributes=commute,hobby

For each custom attribute, the attribute name, value and type will be given. For example:

    "customAttributes": [
        {
            "attributeName": "commute",
            "value": "01:58:00",
            "type": "Duration field"
        },
        {
            "attributeName": "hobby",
            "value": "Cinema",
            "type": "String field"
        }
    ]

For custom attributes of the type Drop-down list or Drop-down list for multiselection, a GET /dropdown/customAttribute/{attributeName} call has been added to the API to retrieve the possible values. The {attributeName} should be replaced with the actual attribute name of the custom attribute.

For example, GET /person/v1/dropdown/customAttribute/payDepartment.

To update one or more custom attributes on a person using the POST or PUT /person calls, an array needs to be provided with their attribute name and value:

    "customAttributes": {
            "payDepartment": "Movies",
            "commute": "01:56:00.000",
            "hobby": "Cinema"
        }

If the value is left empty by using null or "" for some types, the custom attribute is emptied.

The YAML has been updated for these changes.

2021r3.000

Create person without real name

In version 2020r2.002, the person API was adapted to support cast members in the content API.

From that version, on the PSIPersonNameType drop-down list, it became possible to indicate which name types should be added by default when creating a new person. However, it became possible to create a person without a Real name or without the name types that are supposed to be added by default.

This issue has been fixed.

When the real name is not provided in the namesList, the error The namesList should at least include the real name. is returned.

When the names list does not include the name types that should be added by default, the error The namesList should include the [name types marked as add by default]. is returned.

2020r2.000

API version: v1.0.0

Addition of Person API

From this version on, it is possible to manage persons using the Person API and support cast members in the content API.