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

Response schema changed for GET /alerts/{alert-id}/alert_statuses (AlertStatus)

Affected surface
GET /alerts/{alert-id}/alert_statuses
Affected field
AlertStatus

What changed

Response schema changed for GET /alerts/{alert-id}/alert_statuses (AlertStatus) Affected surface: GET /alerts/{alert-id}/alert_statuses. Root cause: schema `AlertStatus`. Detected at Tue, 05 May 2026 03:25:26 UTC UTC.

Diff

{
  "path": "GET /alerts/{alert-id}/alert_statuses",
  "removed_fields": [
    "alert_status"
  ],
  "schema_path": "schema AlertStatus"
}

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.