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

60440: Unsupported verification content type


ERROR: 60440

error-60440 page anchor
VERIFY
ERROR

Twilio returns this error when a Verify request asks for a verification content type that Verify does not support. Start new verification requests support a defined set of channels. They also use different customization options depending on the channel. For example, SMS and Voice use TemplateSid, while email uses channelConfiguration with a Verify email integration.

Possible causes

possible-causes page anchor
  • The request includes a verification content type value that Verify does not recognize or support.
  • The request uses content customization that does not match the selected channel. Verify accepts TemplateSid for SMS and Voice verifications, while email customizations are passed in channelConfiguration.
  • The request is using the email channel without the required Verify email integration. Email verifications require SendGrid setup before you can send customized email verification content.
  • The request is built for a channel outside the supported Verify verification flow. When you start a verification, use one of the supported Verify channels for that endpoint.
  • Review the request sent to the Verifications endpoint and remove any unsupported verification content type values. Then retry the request with a supported Verify channel and its matching parameters.
  • If you are customizing SMS or Voice verification messages, use a valid TemplateSid from your Verify templates instead of an unsupported content type. Verify templates expose the channels they support so you can match the template to the verification channel.
  • If you are sending email verifications, configure a Verify email integration with SendGrid and pass email-specific overrides in channelConfiguration, such as template_id, from, from_name, or substitutions.
  • Retry the verification without custom content to confirm the base request succeeds. If you do not select a specific template and no Service default template is configured, Verify uses the default verification template automatically.

Additional resources

additional-resources page anchor