WhatsApp Cloud API · error code

WhatsApp error 131031: Account has been locked

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, or we were unable to verify data included in the request against data set on the WhatsApp Business Account (e.g, the two-step pin included in the request is incorrect).

What error 131031 means

Code 131031 means the WhatsApp Business Account is locked. Meta gives two distinct reasons in a single message: either the account was restricted or disabled for a policy violation, or the platform could not verify data in your request against what is stored on the account, with the example of an incorrect two-step verification PIN. Those are very different situations that share a code, so the first task is to work out which one you are in.

If the lock follows a registration or PIN change call, the verification failure reading is likely and the account may be temporarily locked after repeated wrong PINs. If it appears on ordinary sends with no registration activity, it is an integrity action similar to 368, and Business Manager's Account Quality page will explain it.

Meta suggests the Health Status API as an additional source, which can show per-node status for the app, WABA, and phone number and often names the blocking reason.

Why it happens

  • A policy violation leading to an account restriction or disable.
  • Repeated registration attempts with a wrong two-step verification PIN.
  • Data in the request (PIN, certificate, or identifiers) not matching what is set on the WABA.
  • An integrity review locking the account pending information from the business.

How to fix WhatsApp error 131031

  1. 1Call GET /{waba-id}?fields=health_status to see which node is blocked and the stated reason.
  2. 2Open Business Manager, Account Quality, and read any restriction and its appeal path.
  3. 3If the trigger was registration, confirm the PIN with whoever set it, reset it if necessary, and wait before retrying to avoid further lock-outs.
  4. 4Stop all outbound traffic until the lock is cleared; continued attempts do not help and may lengthen it.
  5. 5If the reason is a policy action, file an appeal with evidence; the recovery steps in the account restriction guide apply.

How to stop it recurring

Store the two-step verification PIN in a secrets manager alongside the token so automated registration never guesses, and rate-limit registration attempts on your side. For the policy side, monitor quality ratings and Account Quality alerts routinely so restrictions are anticipated, and keep opt-in evidence ready for any appeal. Registration-side lockouts have their own ladder - 133005, then 133008 - described in the registration troubleshooting guide.

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

Related codes

Error 131031 - quick answers

What does WhatsApp error 131031 mean?

Code 131031 means the WhatsApp Business Account is locked. Meta gives two distinct reasons in a single message: either the account was restricted or disabled for a policy violation, or the platform could not verify data in your request against what is stored on the account, with the example of an incorrect two-step verification PIN.

How do I fix WhatsApp error 131031?

1. Call GET /{waba-id}?fields=health_status to see which node is blocked and the stated reason. 2. Open Business Manager, Account Quality, and read any restriction and its appeal path. 3. If the trigger was registration, confirm the PIN with whoever set it, reset it if necessary, and wait before retrying to avoid further lock-outs. 4. Stop all outbound traffic until the lock is cleared; continued attempts do not help and may lengthen it. 5. If the reason is a policy action,…

Stop debugging WhatsApp by hand

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