WhatsApp Error? Fix the Root Cause, Not Just the Symptom

Quick answer: If WhatsApp Business API error 131031 says the business account is locked, start with the lock notice in Meta Business Manager, the exact registered phone number and two-step PIN, and recent API send volume or policy alerts. This is usually caused by account verification problems, trust or policy enforcement, or temporary rate-limit review. Do not reset, reinstall, or wipe anything until these safer checks are complete.

This is an account-level auth and access problem, not a phone or app repair issue. In most cases, the fix is to confirm what Meta locked, correct any verification mismatch, pause sending, and then submit review only after the account details are clean.

Quick Fix Checklist

• Open Meta Business Manager or WhatsApp Manager and check for a lock, restriction, review, quality, or policy notice.
• Confirm the exact phone number on the WhatsApp Business Account matches the number your API integration is using, including country code.
• Verify the two-step verification PIN, recovery email, and any recent ownership or admin changes.
• Review recent message volume, retries, template sends, and automation changes for spikes that may have triggered a trust review.
• Pause bulk sends until the account status is clear, especially if the lock appeared after a campaign or migration.
• Check whether the error appears for one number only or every number under the same business.

Causes

Error 131031 usually means Meta has restricted the WhatsApp Business Account, the phone number, or both. The most common triggers are verification mismatches, policy enforcement, unusual traffic patterns, or a recent registration or migration change.

Cause	What to check	Fix
Business account lock	Status, review, or restriction notice in Meta	Follow the review flow and stop sending until the lock is cleared
Phone number mismatch	Registered number in WABA vs number used by the API	Update integration settings to the exact registered number
Two-step PIN or ownership issue	PIN, recovery email, recent admin or ownership changes	Correct verification details before retrying registration or sends
Rate-limit or abnormal activity	Sudden send spikes, retries, queue loops, webhook failures	Reduce traffic, fix retry storms, and wait for review or unlock
Policy or quality enforcement	Template quality, policy alerts, rejected content	Remove flagged content and submit review if available
Recent migration or re-registration	Old registration still attached or incomplete release	Confirm the previous setup was fully released before re-adding the number

Step-by-Step Fix

1. Sign in to the correct Meta Business Manager that owns the WhatsApp Business Account.
2. Open WhatsApp Manager and identify whether the lock is on the business account, the phone number, or both.
3. Read the exact notice. If Meta shows review, policy, quality, or verification language, use that as the primary branch instead of guessing.
4. Confirm the API is sending from the same phone number registered in the WABA, with the correct country code and no old test number left in the integration.
5. Check two-step verification details. If the PIN was changed, forgotten, or entered incorrectly during re-registration, resolve that first.
6. Review recent changes made by admins, agencies, or developers, including ownership transfers, security changes, webhook edits, token refreshes, and number migrations.
7. Inspect message logs for retry storms, duplicate sends, failed webhooks, or automation loops. These can look like abusive traffic and trigger a temporary lock.
8. Pause campaigns, bulk sends, and automated retries until the account status is normal.
9. If Meta offers an appeal or review button, submit it with the exact error code 131031, affected number, timestamps, and a short explanation of what changed before the lock.
10. After the lock is removed, test with one approved template or one low-volume message before restoring normal traffic.

Still Not Working

If 131031 remains after the basic checks, narrow it down before escalating. The goal is to prove whether the problem is tied to one account object, one admin session, one browser, one token path, or all environments.

• One account only vs all accounts: If only one phone number or WABA shows 131031, the lock is likely object-specific. If every number fails, review business-level restrictions, admin permissions, or portfolio security alerts.
• Browser session issues: If Meta pages do not show the expected lock notice, try another browser, a private window, or another verified admin account. Stale cookies or an outdated session can hide review prompts.
• Another device: Ask a second admin on another device to open the same WhatsApp Manager page. If they can see the restriction and you cannot, your session or permissions may be the issue.
• After an update or integration change: If the error started after a platform update, token rotation, BSP change, webhook edit, or migration, compare the last known working configuration with the current one.
• Wi-Fi vs mobile data: For dashboard access only, if Meta pages fail to load on one network, try another network to rule out local filtering or corporate firewall issues. This does not cause 131031 itself, but it can block the review workflow.
• All networks and all browsers: If the lock appears everywhere, treat it as a confirmed account restriction and stop local troubleshooting.
• Token and permission checks: Make sure the system user, app, and access token still have the required permissions for the same business portfolio. A permission mismatch can confuse diagnosis when a lock and auth issue happen together.
• Queue and cache layers: Clear stuck retry jobs, delayed workers, or cached routing rules in your integration so the system does not keep hammering a locked number. This is a common non-obvious cause of repeated 131031 responses.
• Migration edge case: If the number was recently moved between providers or accounts, confirm the old provider fully released it and that no old webhook or sender profile is still active.
• Escalation: Open a Meta support case from the owning business account and include the exact error code, WABA ID, phone number, timestamps, recent changes, and screenshots of any lock or quality notice.

Only consider reinstalling tools, rotating infrastructure, or rebuilding the integration after Meta confirms the account is unlocked. Reinstalling an app or resetting a device will not remove an account-level lock.

What is error code 131031 business account has been locked?
It means Meta has restricted the WhatsApp Business Account or its phone number. The usual reasons are verification problems, policy or quality enforcement, or unusual sending activity.

How do I unlock my WhatsApp Business API account?
Check the lock notice in Meta Business Manager, verify the registered number and two-step PIN, pause sending, then submit the review or support request shown for that account.

Does error 131031 mean the phone number is permanently banned?
No. It often means the number or WABA is temporarily locked or under review. Check the exact status before assuming the number is permanently blocked.

Can high message volume or retries cause WhatsApp Business API error 131031?
Yes. Sudden traffic spikes, retry loops, duplicate sends, or automation bursts can trigger a trust review or temporary lock.

Why do I see 131031 after re-registering or migrating a number?
Usually because the old registration was not fully released, the PIN or ownership details do not match, or the integration is still pointing to an outdated sender configuration.

Should I reinstall the app or reset anything to fix 131031?
No. This is an account and verification issue. Reinstalling apps or resetting devices does not remove a Meta lock on the business account or phone number.

Frequently Asked Questions