Meta's own WhatsApp error codes, where they appear in Avox, and how each one maps to an Avox API error code.
These are Meta's own error numbers, returned by WhatsApp's Cloud API. They're separate from
Avox's own AVX-XXXX error codes (shown in the dashboard) and from the
Avox API error codes (like template_not_found) your server branches on.
This page covers the codes you're most likely to meet. Meta's developer documentation is the complete, always-current reference - check there for any code not listed here.
When WhatsApp refuses a send made through the Avox API, Avox turns Meta's code into one stable Avox code, so your code only has to handle a short list. Avox checks Meta's code first, then the HTTP status Meta answered with:
Every Meta Graph API error, WhatsApp included, uses the same envelope:
{
"error": {
"message": "(#131047) Re-engagement message",
"type": "OAuthException",
"code": 131047,
"error_data": {
"messaging_product": "whatsapp",
"details": "Message failed to send because more than 24 hours have passed since the customer last replied to this number."
},
"fbtrace_id": "AbCdEf123456"
}
}
code is the number to look up below. The Avox API passes only that number on, as meta_code -
Meta's wording stays out of your responses. An Avox API error looks like this:
{
"ok": false,
"error": {
"code": "outside_messaging_window",
"message": "It's been more than 24 hours since this person last messaged you. Send an approved template instead.",
"docs_url": "https://docs.avox.com/api/errors#outside_messaging_window",
"request_id": "req_4f1c2a9b8e7d6c5b4a3f2e1d",
"meta_code": 131047
}
}
If Meta's signup popup reports an error, the connection wizard shows The connection didn't go through, Meta's own message word for word, AVX-3002, and "Meta error" with its number. Look that number up in Meta's WhatsApp Embedded Signup error reference. The wizard's Try this list covers the usual fixes, and you can click Retry connection. See Embedded Signup for what each step of the popup does.
When Avox can't finish something with Meta for you in the dashboard - changing a template or Flow, updating a number's settings, checking health - you see an Avox AVX code with a plain-English message. With WhatsApp API problem reports on in Compliance, the Switchboard's Owner also gets an email when requests Avox makes to Meta for you keep failing - at most one per issue per week.
Last updated