Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 131000: Something went wrong

Error 131000 is WhatsApp's "something went wrong": the message failed for a reason Meta didn't classify. Most of the time it's transient, but a 131000 that repeats for the same kind of message points to something in the request.

131000
Code
Something went wrong
Meta's name
Meta service
Type
API response or failure webhook
Where you see it
Yes, with backoff
Retry

Quick answer

An unknown error on Meta's side stopped the send. Retry with backoff; if it keeps failing for the same message, check the request and contact support with the trace IDs.

What WhatsApp error 131000 means

Meta documents 131000 as: message failed to send due to an unknown error. Its advice is to try again and, if the error persists, open a support ticket. Meta also notes a specific case for Flows with an endpoint, where setting a business public key failed.

Why error 131000 happens

This one starts on Meta's side, though your request can play a part. Likely causes:

  • A temporary failure inside Meta's systems.
  • An unusual payload Meta's validation doesn't map to a specific code.
  • For WhatsApp Flows with an endpoint, a failure while setting the business public key.

How to fix error 131000

Most of the work is making your sending resilient so this resolves itself.

  • Retry with exponential backoff; one-off 131000 errors usually pass.
  • Check the WhatsApp Business Platform status page for incidents.
  • If one type of message fails every time, compare it with a working message and simplify it.
  • Collect the trace IDs of failing sends and raise a support ticket if it persists.

Should you retry after 131000?

Retry with backoff, and cap the attempts. An error that survives several retries over time needs investigation, not more retries.

How error 131000 shows up in InfiQ

When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 131000, the "(#131000)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. When the failure only shows up after the send was accepted, it arrives as a message.failed webhook whose data.error.metaErrorCode is 131000, tied to the original message. Treat both the same way in your error handling. Keep the trace IDs with the failed message: they are what support needs to look it up. Keep the fbtrace_id from Meta's error object together with the InfiQ_traceid: Meta's support uses the first, InfiQ's support the second.

Send it through InfiQ

Frequently asked questions

Is it safe to retry after error 131000?+
Generally yes, with backoff and a cap. To avoid duplicates, use the same message reference on each retry so you can tell whether an earlier attempt was delivered after all.
Why do I get 131000 when setting up a WhatsApp Flow?+
Meta notes that for Flows with an endpoint, 131000 can come from setting the business public key: the signature couldn't be calculated or an internal call failed. Retry, check the key is a valid 2048-bit RSA public key in PEM format, and contact support if it continues.