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

Response schema changed for POST /v1/workflows/{workflowId}/mailing-list (WorkflowMailingListUpdatedResponse)

Affected surface
POST /v1/workflows/{workflowId}/mailing-list
Affected field
WorkflowMailingListUpdatedResponse

What changed

Response schema changed for POST /v1/workflows/{workflowId}/mailing-list (WorkflowMailingListUpdatedResponse) Affected surface: POST /v1/workflows/{workflowId}/mailing-list. Root cause: schema `WorkflowMailingListUpdatedResponse`. Detected at Fri, 24 Jul 2026 06:42:57 UTC UTC.

Diff

{
  "path": "POST /v1/workflows/{workflowId}/mailing-list",
  "removed_fields": [
    "queuedContactLimitReached"
  ],
  "schema_path": "schema WorkflowMailingListUpdatedResponse"
}

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.