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

Response schema changed for POST /v1/contacts/create (ContactRequest)

Affected surface
POST /v1/contacts/create
Affected field
ContactRequest

What changed

Response schema changed for POST /v1/contacts/create (ContactRequest) Affected surface: POST /v1/contacts/create. Root cause: schema `ContactRequest`. Detected at Wed, 22 Jul 2026 06:06:39 UTC UTC.

Diff

{
  "path": "POST /v1/contacts/create",
  "removed_fields": [
    "userGroup",
    "userId",
    "email",
    "firstName",
    "lastName",
    "mailingLists",
    "subscribed"
  ],
  "schema_path": "schema ContactRequest"
}

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.

Related changes

Other endpoints affected by the same root cause.

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.