New: MCP server monitoring is live. Start free
IncreaseSchemaBehavioral

Response schema changed for GET /check_deposits/{check_deposit_id} (check_deposit)

Affected surface
GET /check_deposits/{check_deposit_id}
Affected field
check_deposit

What changed

Response schema changed for GET /check_deposits/{check_deposit_id} (check_deposit) Affected surface: GET /check_deposits/{check_deposit_id}. Root cause: schema `check_deposit`. Detected at Tue, 28 Apr 2026 23:52:23 UTC UTC.

Diff

{
  "path": "GET /check_deposits/{check_deposit_id}",
  "removed_fields": [
    "lockbox_id"
  ],
  "schema_path": "schema check_deposit"
}

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.