WhatsApp error 131051
Error 131051: Unsupported message type
Error 131051 means the message type is not one WhatsApp supports in that context. You may see it on a message you sent with a type the Cloud API does not accept, and on messages customers send that the Cloud API cannot show, such as some newer WhatsApp features. Send a supported type instead: text, media, a template or a supported interactive message.
- Meta’s description
- “Unsupported message type.” Meta’s error codes, 4 October 2026
- Charged by Meta?
- No. Meta charges only for delivered messages, and this one was not delivered.
Common causes
- Sending a message type the Cloud API does not support, or one not allowed on that number.
- A customer sending something the Cloud API cannot represent, which arrives as an “unsupported” message with no content.
How to fix it
- Use a supported message type, as listed in Meta’s documentation.
- For a customer’s unsupported message, ask them to send it again as text, a photo or a file.
What Fliok does about it
- Fliok treats 131051 on a send as permanent and does not retry it.
- When a customer’s message arrives as unsupported and the AI agent is on (Basic and above), Fliok replies once with a fixed line asking them to send it again as text, a photo or a file. It is sent at most once a day per chat and is not charged to your AI wallet.
- It does not set off an alert for each message.
Meta sets and changes these codes. If anything here disagrees with Meta’s current reference, Meta is right.
No. Meta does not pass the content of an unsupported message to the API, so no platform can show it. Ask the customer to send it again in another form.
Related codes
Other errors you may see
Let Fliok catch it before Meta does
Blank variables, missing header files and closed windows are checked before a message leaves. Start on the Free plan.
Free forever plan · Keep your WhatsApp app · GST invoice on every payment