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

Response schema changed for PUT /v1/partner_managed_companies/{company_uuid}/migrate (Partner-Managed-Company-Migrate-Request)

Affected surface
PUT /v1/partner_managed_companies/{company_uuid}/migrate
Affected field
Partner-Managed-Company-Migrate-Request

What changed

Response schema changed for PUT /v1/partner_managed_companies/{company_uuid}/migrate (Partner-Managed-Company-Migrate-Request) Affected surface: PUT /v1/partner_managed_companies/{company_uuid}/migrate. Root cause: schema `Partner-Managed-Company-Migrate-Request`. Detected at Wed, 20 May 2026 02:34:04 UTC UTC.

Diff

{
  "path": "PUT /v1/partner_managed_companies/{company_uuid}/migrate",
  "removed_fields": [
    "email",
    "external_user_id",
    "ip_address"
  ],
  "schema_path": "schema Partner-Managed-Company-Migrate-Request"
}

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.