Release notes
2026r3
ANCINE functionality in content API
Business impact
In this version, the ANCINE module was introduced, which allows customers to report to the Brazilian regulatory agency for audiovisual works and to check the quotas imposed by ANCINE.
For broadcasters entering the ANCINE registration details in a separate product metadata or content registration system, it should also be possible to send this data to the Mediagenix Base platform via the business APIs.
Therefore, ANCINE functionality has also been added to the Content API.
What changed
-
Added ANCINE registration attributes to content endpoints
-
Added CRT assignment functionality
-
Added endpoints for ANCINE classifications and CRT assignments
-
Breaking change: No
New attributes
For the new ANCINE properties on content level:
-
brazilLocalProduction
Indicates whether the product is locally produced in Brazil. -
brazilLocalProductionNumber
The ANCINE-issued CBP certificate number for the title. -
ancineClassification
The API reference of the ANCINE classification drop-down value. -
crtAssignments
An array of the CRT assignments of the product.
Affected endpoints
The following endpoints were extended with the new attributes mentioned above:
Products:
GET /products/{productId}
Programs / Series / Seasons / Episodes:
-
GET /[product type]/{id} -
POST /[product type] -
PUT /[product type]/{id}
The crtAssignments array is only returned in GET responses.
Examples
Example response of GET /products/{productId}:
{
"ancineClassification": "brazilIndependentProduction",
"brazilLocalProduction": true,
"brazilLocalProductionNumber": "BP93937363",
"crtAssignments": [
{
"id": "9502689344",
"crtNumber": "3737352",
"crtAssignmentDate": "2026-01-01",
"crtExpirationDate": null
}
]
}
New endpoints
ANCINE classifications:
-
GET /ancineClassifications
Retrieve the values for the ANCINE classifications in theancineClassificationattribute.
CRT assignments:
-
POST /crtAssignments
Create or update CRT assignments for a product. -
PUT /crtAssignments/{id}
Update CRT assignments using the external reference.-
The
POST /crtAssignmentsandPUT /crtAssignments/{id}calls support thepropagateToEpisodesandpropagateToVersionsURL parameters.
-
-
GET /crtAssignments/{id}
Retrieve the details of a CRT assignment. -
DELETE /crtAssignments/{id}
Delete CRT assignments.
Examples
Example response of GET /ancineClassifications:
[
{
"id": "publicity",
"name": "00 - Publicity"
},
{
"id": "brazilIndependentProduction",
"name": "01 - Brazil Independent Production"
},
{
"id": "brazilNonIndependentProduction",
"name": "02 - Brazil Non-Independent Production"
}
]
Example request body for POST /crtAssignments:
{
"contentId": "837361522",
"id": "988625882",
"crtNumber": "7372162",
"crtAssignmentDate": "2025-06-04",
"crtExpirationDate": "2032-12-08"
}
API details
New attributes
brazilLocalProduction
Type: boolean
Nullable: true
brazilLocalProductionNumber
Type: string
Nullable: true
ancineClassification
Type: string
Nullable: true
crtAssignments
Type: array
Items: CRT assignment objects
New endpoints
GET /ancineClassifications
Get the possible values for ANCINE classifications.
POST /crtAssignments
Create or update CRT assignment for content.
PUT /crtAssignments/{id}
Update CRT assignment.
GET /crtAssignments/{id}
Retrieve CRT assignment details.
DELETE /crtAssignments/{id}
Remove CRT assignment.
YAML changes
Paths added
-
/ancineClassifications -
/crtAssignments -
/crtAssignments/{id}
New schemas
-
CRTAssignments -
CRTAssignmentsForGet
These include:
-
crtNumber -
crtAssignmentDate -
crtExpirationDate
Updated schemas
Content
Added:
-
brazilLocalProduction -
brazilLocalProductionNumber -
ancineClassification
ContentForGet
Added:
-
brazilLocalProduction -
brazilLocalProductionNumber -
ancineClassification -
crtAssignments
Access
Latest YAML available via: GET /api
Comparison
YAMLs can be compared in more detail using: TextCompare
Improved performance for GET calls with content collection items
When performing a GET call to /products, /episodes, /programs, or similar endpoints for a product that is part of a content collection, the response could take longer than expected when the content collection contained a large number of items (for example, thousands).
This issue has been fixed. The logic has been optimised so that content collection items are retrieved more quickly for the queried product.