Fields removed in POST /v3/application/shops/{shop_id}/listings request body: [personalization_char_count_max is_personalizable personalization_is_required pers…

What changed

Fields removed in POST /v3/application/shops/{shop_id}/listings request body: [personalization_char_count_max is_personalizable personalization_is_required personalization_instructions] Affected surface: POST /v3/application/shops/{shop_id}/listings. Root cause: endpoint `POST /v3/application/shops/{shop_id}/listings`. Detected at Tue, 01 Sep 2026 10:56:24 UTC UTC.

Diff

{
  "path": "POST /v3/application/shops/{shop_id}/listings",
  "removed_fields": [
    "personalization_char_count_max",
    "is_personalizable",
    "personalization_is_required",
    "personalization_instructions"
  ],
  "schema_path": "POST /v3/application/shops/{shop_id}/listings request body"
}

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.