New: MCP server monitoring is live. Start free trial
EtsySchemaBehavioral

Fields removed in PATCH /v3/application/shops/{shop_id}/listings/{listing_id} request body: [personalization_is_required personalization_char_count_max is_perso…

Fields removed in PATCH /v3/application/shops/{shop_id}/listings/{listing_id} request body: [personalization_is_required personalization_char_count_max is_personalizable personalization_instructions]

Affected surface
PATCH /v3/application/shops/{shop_id}/listings/{listing_id}

What changed

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

Diff

{
  "path": "PATCH /v3/application/shops/{shop_id}/listings/{listing_id}",
  "removed_fields": [
    "personalization_is_required",
    "personalization_char_count_max",
    "is_personalizable",
    "personalization_instructions"
  ],
  "schema_path": "PATCH /v3/application/shops/{shop_id}/listings/{listing_id} 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.

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

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.