WhatsApp Cloud API · error code

WhatsApp error 368: Temporarily blocked for policies violations

Policy / accountHTTP 403Account integrity & policy

Last verified against Meta for Developers - Cloud API error codes

What WhatsApp returns
The WhatsApp Business Account associated with the app has been restricted or disabled for violating a platform policy.

What error 368 means

Code 368 is an account-level enforcement action, not a per-message problem. Meta has restricted or disabled the WhatsApp Business Account your app is using because it found a violation of the WhatsApp Business Messaging Policy or Commerce Policy. Every send from every phone number on that WABA will fail with 368 until the restriction is lifted; changing tokens, templates, or recipients does nothing.

The restriction can be temporary with an end date, or it can be an outright disable pending appeal. Details appear in Business Manager under Account Quality, and Meta usually emails the admins. Common triggers include repeated low-quality template sends, selling prohibited goods, messaging people without opt-in, and content that recipients report at a high rate.

This is different from 131048 (quality-based rate limit) and 131031 (account locked, which also covers failed data verification). 368 is a policy judgment about the account as a whole.

Why it happens

  • Sustained high block and report rates across templates, leading to an enforcement action.
  • Messaging content or products that violate the Commerce Policy or Business Messaging Policy.
  • Sending business-initiated messages without documented opt-in.
  • Multiple WABAs under one portfolio with shared bad signals, so the enforcement spreads.
  • A prior warning or temporary restriction that was not addressed.

How to fix WhatsApp error 368

  1. 1Open Business Manager, Account Quality, and read the exact violation, its scope, and any end date.
  2. 2Stop all outbound campaigns immediately so further signals do not worsen the case.
  3. 3Review templates and flows against the WhatsApp Business Messaging Policy and remove anything that could have triggered it.
  4. 4If you believe it is mistaken, file the appeal from Account Quality and include evidence of opt-in and content compliance.
  5. 5Once the restriction lifts, resume slowly with utility content to rebuild quality before marketing volume.
  6. 6See the account restriction recovery guide at /blog/whatsapp-business-account-restricted for the appeal timeline.

How to stop it recurring

Monitor template quality ratings and phone number status in WhatsApp Manager weekly, and pause any template that drops to Medium before it drops to Low. Keep auditable opt-in records, segment marketing by engagement, and run new templates through the policy checklist before submission. Separate high-risk experimental sends onto a dedicated WABA so a mistake cannot restrict your core number. Watch the indicators under quality rating and status, and treat 131048 as the number-level warning shot that precedes account enforcement.

Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.

Related codes

Error 368 - quick answers

What does WhatsApp error 368 mean?

Code 368 is an account-level enforcement action, not a per-message problem. Meta has restricted or disabled the WhatsApp Business Account your app is using because it found a violation of the WhatsApp Business Messaging Policy or Commerce Policy. Every send from every phone number on that WABA will fail with 368 until the restriction is lifted; changing tokens, templates, or recipients does nothing.

How do I fix WhatsApp error 368?

1. Open Business Manager, Account Quality, and read the exact violation, its scope, and any end date. 2. Stop all outbound campaigns immediately so further signals do not worsen the case. 3. Review templates and flows against the WhatsApp Business Messaging Policy and remove anything that could have triggered it. 4. If you believe it is mistaken, file the appeal from Account Quality and include evidence of opt-in and content compliance. 5. Once the restriction lifts, resume…

Stop debugging WhatsApp by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.