Reselling Products / WhatsApp
WhatsApp: Unsupported Message Type
Modified on: Mon, 11 May, 2026 at 4:07 AM
Troubleshooting Guide WhatsApp: Unsupported Message Type Understand why some messages appear as unsupported in OmniReach, what message types are supported, and how to resolve error code 131051. |
TABLE OF CONTENTS
- What is an Unsupported Message Type?
- Error Code 131051 Explained
- Supported Message Types in OmniReach
- Unsupported Message Types
- How Unsupported Messages Appear in OmniReach
- How to Resolve This
- Frequently Asked Questions
What is an Unsupported Message Type? Why some messages cannot be displayed or sent through the WhatsApp Business API |
WhatsApp offers many message types in the consumer app — stickers, polls, voice notes, GIFs, contact cards, and more. However, the WhatsApp Business Platform (Cloud API) that powers OmniReach only supports a specific set of message types.
When a customer sends a message type that the Business API does not support — such as a poll or a deleted message — OmniReach cannot display or process it. Instead, you will see a notification indicating that the message is unsupported.
This is not a bug in OmniReach — it is a limitation set by Meta's WhatsApp Business Platform API. The same restriction applies to all CRM platforms built on the API.
Error Code 131051 — Unsupported Message Type What this error means and when it occurs |
Meta assigns the error code 131051 when a message type is not supported by the WhatsApp Business API. This error appears in two situations:
| |
|
Title: Unsupported message type
Details: Message type is not currently supported
Type returned:
unknown or unsupported✓ Supported Message Types in OmniReach These message types are fully supported by the WhatsApp Business Platform API |
The following message types can be sent and received through OmniReach's WhatsApp integration:
| Message Type | Direction | Details |
|---|---|---|
| Text | Both | Plain text messages, including emojis and links |
| Image | Both | JPEG, PNG. Max 5MB |
| Video | Both | MP4, 3GPP. Max 16MB |
| Audio | Both | AAC, MP4, MPEG, AMR, OGG (audio). Max 16MB |
| Document | Both | PDF, Word, Excel, PowerPoint, and more. Max 100MB |
| Sticker | Both | Static WebP (outbound). Animated WebP (inbound only) |
| Location | Both | Share or receive a map pin with coordinates |
| Template Messages | Outbound | Pre-approved Marketing, Utility, and Authentication templates |
| Interactive | Outbound | List messages, Reply buttons, CTA URL buttons |
| Contacts | Both | Structured contact cards via the API only |
| Reaction | Both | Emoji reactions to messages (API v2.45+) |
✘ Unsupported Message Types These types cannot be displayed or processed through the WhatsApp Business API |
The following message types are not supported by the WhatsApp Business Platform API. If a customer sends any of these, they will appear as an unsupported message in OmniReach and you will not be able to see the content:
|
| ||
|
| ||
|
| ||
|
|
How Unsupported Messages Appear in OmniReach What you'll see in your conversation view when an unsupported message is received |
When a customer sends an unsupported message type, OmniReach displays a placeholder in the conversation thread. Depending on the message type, you may see:
| |
| |
|
The message will still appear as received in OmniReach — you will know the customer sent something, but the contents cannot be read. You can still reply to the contact normally.
How to Resolve This Steps to take when you encounter unsupported message type errors |
| |
| |
| |
|
Frequently Asked Questions Common questions about unsupported message types |
❓ A customer sent me a poll — why can't I see it in OmniReach? Polls are not supported by the WhatsApp Business Platform API. When a customer sends a poll, OmniReach receives a webhook with error code 131051 and the message appears as unsupported. There is no way to view the poll content — ask the customer to share their response as a text message instead. |
❓ Is this a bug in OmniReach? No. This is a limitation of Meta's WhatsApp Business Platform API. Every CRM and messaging platform built on the API — including OmniReach — has the same restriction. It cannot be worked around. |
❓ Can I still reply to a customer who sent an unsupported message? Yes. Even though you cannot see the content of the unsupported message, the conversation is still open. You can reply normally using any supported message type such as text, image, or audio. |
❓ A customer deleted a message — can I recover what they sent? No. Deleted messages are not recoverable through the API. Once a message is deleted by the customer, neither OmniReach nor Meta's servers will have a record of its content. |
❓ Will Meta add support for polls and GIFs in the future? Meta periodically expands the Business API's capabilities. Reactions, for example, were added in a later API version. Keep an eye on Meta's WhatsApp Business Platform changelog for updates. OmniReach will incorporate new supported types as Meta makes them available. |
❓ I'm getting error 131051 when sending a message — what should I check? Verify that the message type you are sending is in the supported list above. Common causes include sending an animated GIF, using an incorrect API parameter, or attempting to send a message to another WhatsApp Business API account (business-to-business messaging is not supported by Meta). |
? Quick Tip To avoid confusion with customers, consider adding an automated reply in OmniReach that triggers when an unsupported message is received — letting the customer know their message couldn't be read and asking them to resend as text, image, audio, or document. |
