New fields added in GET /v1/customers/{customer_id}/subscription_preferences response 400: [errors]

What changed

New fields added in GET /v1/customers/{customer_id}/subscription_preferences response 400: [errors] Affected surface: GET /v1/customers/{customer_id}/subscription_preferences. Root cause: endpoint `GET /v1/customers/{customer_id}/subscription_preferences`. Detected at Fri, 28 Aug 2026 23:54:43 UTC UTC.

Diff

{
  "added_fields": [
    "errors"
  ],
  "path": "GET /v1/customers/{customer_id}/subscription_preferences",
  "schema_path": "GET /v1/customers/{customer_id}/subscription_preferences response 400"
}

Likely impact

This is an additive change. Existing integrations are unaffected; this is mostly useful if you want to take advantage of the new surface.

Recommended action

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