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

Enum values changed in GET /v2/Conversations/{ConversationId}/Communications/{id} (conversations.v2.recipient_delivery_status)

Affected surface
GET /v2/Conversations/{ConversationId}/Communications/{id}
Affected field
conversations.v2.recipient_delivery_status

What changed

Enum values changed in GET /v2/Conversations/{ConversationId}/Communications/{id} (conversations.v2.recipient_delivery_status) Affected surface: GET /v2/Conversations/{ConversationId}/Communications/{id}. Root cause: schema `conversations.v2.recipient_delivery_status`. Detected at Fri, 28 Aug 2026 15:12:15 UTC UTC.

Diff

{
  "added_enums": [
    "READ"
  ],
  "path": "GET /v2/Conversations/{ConversationId}/Communications/{id}",
  "schema_path": "schema conversations.v2.recipient_delivery_status"
}

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.

Audit any switch/match statements over this enum. Removed values become unhandled paths.

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.