Release notes

2022r7

Fix for POST /sportEvents call in sport API

Previously, when

• creating a sport event for a season through the POST /sportEvents call of the sport API,

• linking an episode to that event,

• updating the event through the POST /sportEvents call with the same body,

then the update would not be done even though nothing had changed, and the following error response was given:

{
    "statusCode": "422",
    "message": "Operation cannot be completed due to violations",
    "timestamp": "2022-11-16T10:29:39Z",
    "concept": "SportEvent",
    "id": "10850401002",
    "errors": [
        {
            "errorCode": "SPORT-00014",
            "description": "$_A sport event which has content linked to it cannot be moved to a different season",
            "data": []
        }
    ]
}

This issue has been fixed and the update is now done in this scenario.

2020r1.002

API version: v1.0.0

External reference cannot be cleared by BAPI

Within any POST and PUT call, if a an attribute is sent empty, WHATS'ON will clear that field. Previously, this was also possible with the external reference of a sport league, season, event, player or team.

Now, this is fixed. When no external reference is provided but the attribute is sent empty or Null, we will ignore that tag and proceed as if there was no ID field (external reference) provided. This means that it should remain as is in a PUT call or return a new one in a POST call.

2017r1.006

API version: v1.0.0

Addition of On-demand schedule API

From this version on, it is possible to manage on-demand transmissions using the On-demand schedule API.