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

50542: Unsupported Content Template Type


ERROR: 50542

error-50542 page anchor
ERROR

This error occurs when you send a Content Template through Conversations and the template uses a content type that Conversations does not support. Conversations currently supports twilio/text, twilio/media, twilio/location, twilio/quick-reply, twilio/call-to-action, twilio/list-picker, and twilio/card.

Possible causes

possible-causes page anchor
  • The template uses a content type that appears in Content Template Builder but is not listed among the content types currently supported by Conversations. Examples include twilio/carousel, twilio/catalog, twilio/pay, twilio/flows, whatsapp/card, and whatsapp/authentication.
  • Your application selected or reused a template without checking its types object first. The Content API returns each template with a types field, and you can fetch a single template with GET /v1/Content/{ContentSid} or list templates with GET /v1/Content.
  • You created a template for another sending path and then tried to send it through Conversations. Content Templates can be sent across multiple Twilio products, but Conversations supports a narrower set of content types than the full set available in Content Template Builder.
  • Use a Conversations-supported content type. Recreate the template or choose a different template that uses twilio/text, twilio/media, twilio/location, twilio/quick-reply, twilio/call-to-action, twilio/list-picker, or twilio/card.
  • Inspect the template before sending it. Verify the template type in Content Template Builder, or fetch the template through the Content API and review the types object returned for the ContentSid.
  • Add validation to your application so requests sent through Conversations use only the template types documented as supported by Conversations. Keep a fallback template in a supported type such as twilio/text or twilio/card when you need to send through Conversations. This recommendation is based on the supported Conversations type list and the Content API template schema.

Additional resources

additional-resources page anchor