Schema reference changed in POST /api/whatsApp/cancel request body: "CancelScheduledMessageRequest - campaignId OR scheduledMessageId are required" → "CancelS…
Schema reference changed in POST /api/whatsApp/cancel request body: "CancelScheduledMessageRequest - campaignId OR scheduledMessageId are required" → "CancelScheduledMessageRequest"
- Affected surface
- POST /api/whatsApp/cancel
What changed
Schema reference changed in POST /api/whatsApp/cancel request body: "CancelScheduledMessageRequest - campaignId OR scheduledMessageId are required" → "CancelScheduledMessageRequest" Affected surface: POST /api/whatsApp/cancel. Root cause: endpoint `POST /api/whatsApp/cancel`. Detected at Wed, 26 Aug 2026 13:02:07 UTC UTC.
Diff
{
"current_value": "CancelScheduledMessageRequest",
"path": "POST /api/whatsApp/cancel",
"previous_value": "CancelScheduledMessageRequest - campaignId OR scheduledMessageId are required",
"schema_path": "POST /api/whatsApp/cancel request body"
}Likely impact
This is an additive change. Existing integrations are unaffected; this is mostly useful if you want to take advantage of the new surface.
Recommended action
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.
