Skip to contentSkip to navigationSkip to topbar
Page toolsOn this pageProducts used
Looking for more inspiration?Visit the

23006: Message Redaction Incompatible Configuration: Inbound Webhook GET Requests


WARNING: 23006

warning-23006 page anchor
MESSAGING
WARNING

This warning occurs when Message Redaction is enabled on your account and an incoming message webhook uses GET. To preserve Message Body Redaction or Phone Number Redaction, configure inbound message webhooks for Twilio phone numbers and Messaging Services to use POST instead. GET request parameters are logged for up to seven days.

Possible causes

possible-causes page anchor
  • A Twilio phone number is configured with smsMethod set to GET for its incoming message webhook.
  • A Messaging Service is configured with inboundMethod set to GET. If the service uses the phone number webhook for inbound handling, the sender's phone number configuration can also trigger this warning.
  • A fallback webhook for a Twilio phone number or Messaging Service uses GET. Message Redaction requires POST on both the primary and fallback webhook paths.
  • Update each affected Twilio phone number to use POST for its incoming message webhook by setting smsMethod to POST.
  • Update each affected Messaging Service to use POST for inboundMethod.
  • If your Messaging Service defers inbound handling to sender webhooks, review every sender in the pool and change any incoming message webhook method from GET to POST.
  • Change the fallback webhook method to POST for both phone numbers and Messaging Services.
  • Verify the webhook method anywhere inbound message handling is configured, including the Phone Numbers, Messaging Services, and TwiML Apps sections of Console.

Additional resources

additional-resources page anchor