Question
What does the Unsupported Type callback do?
Applies To
- Messages API
- Unsupported Type Callback
Answer
Unsupported Type callbacks were made available in September 2020. When a social channel (WhatsApp, Viber, Facebook Messenger) releases a feature that Vonage has not yet implemented, we send a callback letting our customers know that this type of message is unsupported.
The Unsupported type callback helps improve the overall developer experience.
For example, if a customer is using a chatbot or AI, they may want to be able to recognize an Unsupported type message in the callback, so that they may then respond with something like, “I’m sorry I can’t see that last message. Can you send as text?”
If any new inbound message types are released across our supported message channels, they will immediately be flagged as unsupported so no additional development work will be required to add them.
Additional Information
For more information on our inbound messages capabilities, see our developer documentation.
Articles in this section
- What is the Messages API sandbox rate limit?
- Why do I receive pricing on all outbound Whatsapp messages that are part of a Conversation?
- Why am I getting Unsupported Type Messages API callbacks?
- What do are the technical requirements needed to implement the Messages API?
- Which IP addresses should I allow for the Vonage Messages and Dispatch APIs?
- How long does Vonage retry inbound messages for the SMS, Messages and Dispatch APIs?
- Which webhook would be used for Messages and Dispatch APIs?