Response schema changed for POST /v1/update_customer_property_definition (CustomerPropertyTypeConfigurationUpdate)

What changed

Response schema changed for POST /v1/update_customer_property_definition (CustomerPropertyTypeConfigurationUpdate) Affected surface: POST /v1/update_customer_property_definition. Root cause: schema `CustomerPropertyTypeConfigurationUpdate`. Detected at Mon, 17 Aug 2026 16:17:54 UTC UTC.

Diff

{
  "path": "POST /v1/update_customer_property_definition",
  "removed_fields": [
    "format"
  ],
  "schema_path": "schema CustomerPropertyTypeConfigurationUpdate"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Recommended action

Diff your serializers against the new schema. The diff above shows what moved.