New: MCP server monitoring is live. Start free
FrontSchemaBreaking

New required fields added in schema ConversationResponse: [links is_private scheduled_reminders _links subject status ticket_ids assignee recipient custom_field…

New required fields added in schema ConversationResponse: [links is_private scheduled_reminders _links subject status ticket_ids assignee recipient custom_fields metadata id tags]

Affected surface
schema ConversationResponse
Affected field
ConversationResponse

What changed

New required fields added in schema ConversationResponse: [links is_private scheduled_reminders _links subject status ticket_ids assignee recipient custom_fields metadata id tags] Affected surface: schema ConversationResponse. Root cause: schema `ConversationResponse`. Detected at Mon, 08 Sep 2025 16:52:10 UTC UTC.

Diff

{
  "added_required": [
    "links",
    "is_private",
    "scheduled_reminders",
    "_links",
    "subject",
    "status",
    "ticket_ids",
    "assignee",
    "recipient",
    "custom_fields",
    "metadata",
    "id",
    "tags"
  ],
  "schema_path": "schema ConversationResponse"
}

Likely impact

Existing integrations relying on this surface will fail or behave incorrectly. Treat this as a release-blocker until the recommended action below is applied.

Add the new required field to all request payloads or arguments. Requests omitting it will be rejected.

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.