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

Schema reference changed in PUT /v1/partner_managed_companies/{company_uuid}/terms_of_service request body: "inline:object" → "Partner-Managed-Company-Retriev…

Schema reference changed in PUT /v1/partner_managed_companies/{company_uuid}/terms_of_service request body: "inline:object" → "Partner-Managed-Company-Retrieve-Terms-Of-Service-Request"

Affected surface
PUT /v1/partner_managed_companies/{company_uuid}/terms_of_service

What changed

Schema reference changed in PUT /v1/partner_managed_companies/{company_uuid}/terms_of_service request body: "inline:object" → "Partner-Managed-Company-Retrieve-Terms-Of-Service-Request" Affected surface: PUT /v1/partner_managed_companies/{company_uuid}/terms_of_service. Root cause: endpoint `PUT /v1/partner_managed_companies/{company_uuid}/terms_of_service`. Detected at Wed, 20 May 2026 02:34:04 UTC UTC.

Diff

{
  "current_value": "Partner-Managed-Company-Retrieve-Terms-Of-Service-Request",
  "path": "PUT /v1/partner_managed_companies/{company_uuid}/terms_of_service",
  "previous_value": "inline:object",
  "schema_path": "PUT /v1/partner_managed_companies/{company_uuid}/terms_of_service request body"
}

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.

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.