New: MCP server monitoring is live. Start free trial
Webex (Messaging)SchemaBehavioral

Response schema changed for GET /hds/clusters/{clusterId} (clusterDetailsResponse)

Affected surface
GET /hds/clusters/{clusterId}
Affected field
clusterDetailsResponse

What changed

Response schema changed for GET /hds/clusters/{clusterId} (clusterDetailsResponse) Affected surface: GET /hds/clusters/{clusterId}. Root cause: schema `clusterDetailsResponse`. Detected at Thu, 14 May 2026 00:25:22 UTC UTC.

Diff

{
  "path": "GET /hds/clusters/{clusterId}",
  "removed_fields": [
    "items"
  ],
  "schema_path": "schema clusterDetailsResponse"
}

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.