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

Response schema changed for GET /subscriptions/{subscription-id}/applicable_alerts (Alert)

Affected surface
GET /subscriptions/{subscription-id}/applicable_alerts
Affected field
Alert

What changed

Response schema changed for GET /subscriptions/{subscription-id}/applicable_alerts (Alert) Affected surface: GET /subscriptions/{subscription-id}/applicable_alerts. Root cause: schema `Alert`. Detected at Tue, 05 May 2026 03:25:26 UTC UTC.

Diff

{
  "path": "GET /subscriptions/{subscription-id}/applicable_alerts",
  "removed_fields": [
    "alarm_triggered_at",
    "scope"
  ],
  "schema_path": "schema Alert"
}

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.