The account_review_update field reports Meta's review decision for a WhatsApp Business Account (WABA). It is useful for account readiness and onboarding state, especially when a WABA cannot yet use APIs.
What account_review_update Reports
This field reports the WABA review outcome through a single decision value.
| Decision | Meaning |
|---|---|
APPROVED | The WABA passed review and can be used with APIs. |
REJECTED | The WABA did not meet policy requirements and cannot be used with APIs. |
PENDING | Review is still pending; API use may be blocked. |
DEFERRED | Meta deferred the decision; API use is blocked until it decides. |
When It Fires
Meta sends this webhook when a WABA is approved, rejected, pending, or deferred after review against WhatsApp policy guidelines.
Payload Shape
{
"object": "whatsapp_business_account",
"entry": [
{
"id": "<WABA_ID>",
"time": 1739321024,
"changes": [
{
"field": "account_review_update",
"value": {
"decision": "APPROVED"
}
}
]
}
]
}Dualhook Handling
Dualhook subscription: subscribed and forwarded. Dualhook's Meta app subscribes to account_review_update. Meta does not allow Webhook Override for account-level fields, so it always arrives on Dualhook's app-level callback.
Dualhook uses it to keep account-readiness signals current, surface review outcomes in operational views, and forward the event to your configured endpoint.
This field never contains message bodies, contacts, or media. Dualhook stores only the operational event metadata and delivery status needed for monitoring and auditability.
Implementation Notes
- Treat non-
APPROVEDdecisions as account-readiness blockers until Meta changes the decision or the business remediates the issue. - Store the WABA ID and event timestamp for audit trails.
- Do not assume
PENDINGandDEFERREDmean the same thing. Both block use, butDEFERREDusually indicates Meta needs more signal or more information. - Pair this field with
account_alertsandaccount_updatefor a fuller account-health picture.