Breaking
New required request property: fields
openapi:POST /structured-contents::request.application.json.content_body.fields.additionalProperties.items.field_values.items.anyOf[#.components.schemas.ContentFieldValueWithEmbeddedModel].content_details.fields- Product
- Optimizely Content Marketing Platform
- Source
- OpenAPI URL
- Change kind
- New Required Request Property
- Detected
- Last updated
Deterministic evidence
Before / after
Extracted from Optimizely's published contract. Shows the schema the change belongs to. Open the source ↗
{
{
"additionalProperties": {
"items": {
"$ref": "#/components/schemas/LocalizedFieldValuesWithEmbeddedContent"
},
"type": "array"
},
"properties": {
"properties": {
"content_type_guid": {
"content_type_guid": {
"title": "Contenttypeguid",
"title": "Contenttypeguid",
"title": "Expirydatetime",
"title": "Expirydatetime",
"type": "string"
"type": "string"
},
},
"fields": {
"additionalProperties": {
"items": {
"$ref": "#/components/schemas/LocalizedFieldValuesWithEmbeddedContent"
},
"type": "array"
},
"title": "fields",
"type": "object"
},
"root_content": {
"root_content": {
"title": "Rootcontent",
"title": "Rootcontent",
"type": "boolean"
"type": "boolean"
},
},
"required": [
"required": [
"content_type_guid",
"content_type_guid",
"root_content"
"root_content",
"title",
"fields"
],
],
"type": "object"
"type": "object"
}
}
Monitored for you
Does this change affect your integration?
Choose the operations and fields your services use. Detektu matches Optimizely findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.