New: MCP server monitoring is live. Start free
TwilioSchemaAdditive

New fields added in POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Transcriptions.json request body: [ConversationConfiguration ConversationId]

Affected surface
POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Transcriptions.json request body

What changed

New fields added in POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Transcriptions.json request body: [ConversationConfiguration ConversationId] Affected surface: POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Transcriptions.json request body. Root cause: endpoint `POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Transcriptions.json request body`. Detected at Tue, 10 Mar 2026 08:28:35 UTC UTC.

Diff

{
  "added_fields": [
    "ConversationConfiguration",
    "ConversationId"
  ],
  "schema_path": "POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Transcriptions.json 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.

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.