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

Response schema changed for PUT /api/v1/device-assurances/{deviceAssuranceId} (DeviceAssurance)

Affected surface
PUT /api/v1/device-assurances/{deviceAssuranceId}
Affected field
DeviceAssurance

What changed

Response schema changed for PUT /api/v1/device-assurances/{deviceAssuranceId} (DeviceAssurance) Affected surface: PUT /api/v1/device-assurances/{deviceAssuranceId}. Root cause: schema `DeviceAssurance`. Detected at Mon, 13 Jul 2026 08:48:10 UTC UTC.

Diff

{
  "path": "PUT /api/v1/device-assurances/{deviceAssuranceId}",
  "removed_fields": [
    "devicePostureChecks"
  ],
  "schema_path": "schema DeviceAssurance"
}

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.