New: MCP server monitoring is live. Start free
TwilioSchemaAdditive

Enum values changed in POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Payments/{Sid}.json (payments_enum_capture)

Affected surface
POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Payments/{Sid}.json
Affected field
payments_enum_capture

What changed

Enum values changed in POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Payments/{Sid}.json (payments_enum_capture) Affected surface: POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Payments/{Sid}.json. Root cause: schema `payments_enum_capture`. Detected at Tue, 10 Mar 2026 08:28:35 UTC UTC.

Diff

{
  "added_enums": [
    "postal-code-matcher",
    "payment-card-number-matcher",
    "expiration-date-matcher",
    "security-code-matcher"
  ],
  "path": "POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Payments/{Sid}.json",
  "schema_path": "schema payments_enum_capture"
}

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.