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

Response schema changed for POST /metered_features/{metered-feature-id}/reactivate_command (Meter)

Affected surface
POST /metered_features/{metered-feature-id}/reactivate_command
Affected field
Meter

What changed

Response schema changed for POST /metered_features/{metered-feature-id}/reactivate_command (Meter) Affected surface: POST /metered_features/{metered-feature-id}/reactivate_command. Root cause: schema `Meter`. Detected at Thu, 23 Jul 2026 05:18:26 UTC UTC.

Diff

{
  "path": "POST /metered_features/{metered-feature-id}/reactivate_command",
  "removed_fields": [
    "feature_id",
    "meter_strategy",
    "feature_ids"
  ],
  "schema_path": "schema Meter"
}

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.