What error 131051 is
Error 131051 reaches you in a messages webhook with the type unsupported. The message was delivered to your WhatsApp number, but Meta does not pass that kind of message to the Cloud API, so any inbox or chatbot connected through the API gets the error and no content.
The customer sees nothing unusual. On a Coexistence number, where the WhatsApp Business App and the API share one number, the message is in the Business App on the phone.
Meta often says what the message was. The webhook carries a hint (the unsupported type), such as poll_creation or group_invite. When there is no hint, it shows only as Unsupported.
The causes, most common first
These are the causes we have confirmed on Coexistence numbers, in the order we see them most often.
1. A message from another business's WhatsApp API number
When a number on the WhatsApp API messages another number on the API, most of what it sends arrives as 131051. This is common when a supplier, bank or delivery service with its own chatbot messages your business.
The hint can be any of: list, button, interactive, view_once, hsm (a template message), product, order, media_placeholder or plain Unsupported.
2. "Request contact information" sent from the Business App
When someone on your team sends a request for contact information from the WhatsApp Business App, the copy of that message the API receives (the echo) arrives as 131051 with the hint interactive.
3. Several photos sent at once
When a customer sends several photos in one go, WhatsApp fires an extra webhook before the photos. It is not a message, and the photos themselves arrive after it as their own messages. It shows as Unsupported.
4. A poll
A poll arrives with the hint poll_creation, and a vote on one with poll_update.
5. A group invite
When someone invites the business to a group and the Business App is set so it cannot be added to groups automatically, the invite arrives with the hint group_invite.
6. A calendar event
An event shared in the chat shows as Unsupported, with no hint.
How Volty shows these messages
Volty keeps each one in the conversation as a notice that says what it was, when Meta named it:
A Why? link beside the notice explains that the message is on the phone and that Meta does not pass these types to connected apps. Several photos sent at once show as the photos, without the extra notice. Volty's AI agent does not reply to a message it cannot read.
What to do
1. Open the WhatsApp Business App on the phone and read the message there.
2. Reply if it needs a reply, from the app or from your inbox now that you know what it said.
3. Nothing needs fixing. The message was delivered, and the customer does not need to resend it.
If a contact sends you menus and buttons every time, it is usually another business's chatbot. A reply in plain text still reaches it.
131051 on a message you send
The same code can come back on a message your business sends through the API, when the message type you sent is not supported. Check that the message is one of the types Meta's Cloud API documents for sending, and send it as that type.
Frequently asked questions
Related errors
Start free trial. Our team can help you set up Coexistence and read these messages in one inbox.









