Why am I getting "Unsupported" Type Messages API callbacks?

What does the “Unsupported Type” callback do?

Enhanced Support for Inbound Message Types

As part of a series of improvements we continue to launch on our Messages API, we now offer “Unsupported Type” in our callbacks.  This enhancement went live for all Vonage customers on September 15, 2020.

Previously, when we received a type of inbound message that we did not fully support (for example Whatsapp Stickers) no content would be sent onto our customers. Now, we send on a callback letting our customers know that this type of message is unsupported

When a social channel (WhatsApp, Viber, Facebook Messenger) releases a new feature that Vonage has not yet implemented, the “Unsupported" type callback can help 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, please can you send as text”.  

This capability has been designed so that 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. 

You can view more information on our inbound messages capabilities  on our developer documentation here.  If you have any questions about this new feature, please  contact us. 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request