WhatsApp API Error 131031: "Business Account Locked" — What It Means and How to Fix It Fast

TL;DR

Error 131031 means Meta has indefinitely locked your WhatsApp Business Account. It's caused by either a policy violation (spam, wrong templates, restricted products, incomplete profile) or a two-step PIN mismatch. Check Business Support Home first — if a violation is listed, fix it and file an appeal (24–48 hrs). If nothing is listed, reset your 2-step PIN and re-register the number. Still stuck? Open a Meta Direct Support ticket with your WABA ID and error code 131031.

Introduction

If your WhatsApp Business messages suddenly stopped sending and you're seeing error code 131031, you're not alone. This is one of the most common — and most stressful — errors businesses face on the WhatsApp Business Platform. The good news? It's fixable. This guide will walk you through exactly what's happening, why it happened, and the step-by-step path to getting your account back online.

What Does Error 131031 Actually Mean?

When you see this in your API response:

{
  "error": {
    "code": 131031,
    "title": "Business Account locked",
    "message": "Business Account locked"
  }
}

It means Meta has placed a lock on your WhatsApp Business Account (WABA). Unlike a temporary block that lifts automatically after a few days, a lock is an indefinite freeze — no messages go out, no new numbers can be added, and everything stays paused until you take action to resolve it.

Think of it like your bank freezing a card. The account still exists, nothing is permanently gone, but you can't do anything until the issue is cleared.

Why Did This Happen? The Two Root Causes

Error 131031 always comes down to one of two things. Knowing which one you're dealing with will save you a lot of time.

Cause 1: A Policy Violation

Meta flagged your account for activity that goes against the WhatsApp Business Messaging Policy, Commerce Policy, or Business Terms of Service. This is the more serious of the two causes — but it's still very often reversible.

Common reasons businesses get flagged include:

• Sending unsolicited or bulk messages to users who didn't opt in
• Too many user complaints — when people block your number or report your messages as spam, Meta notices
• Promoting restricted products or services — things like alcohol, tobacco, adult content, supplements, gambling, or pharmaceuticals that violate WhatsApp's Commerce Policy
• Template misclassification — using a utility or authentication template to send what is actually a marketing message
• Missing or invalid business website on your WABA profile
• Incomplete business verification in Meta Business Manager

Meta typically escalates enforcement in steps: a warning first, then short-duration blocks (1, 3, 5, 7, or 30 days), and then a full account lock if the issues aren't resolved. If you're at the lock stage, it means prior warnings may have been missed or not acted on.

Cause 2: A Two-Step PIN or Verification Mismatch

This is a more technical cause but surprisingly common — especially during API setup, number migrations, or when someone resets credentials without updating everything. It means Meta tried to verify a piece of data in your API request (usually a two-step verification PIN) and it didn't match what's on file for the account.

If your account was recently set up, migrated to a new provider, or had its PIN changed, this is likely the culprit. The fix here is simpler and faster than a policy appeal.

How to Diagnose Which One You Have

Before jumping into fixes, you want to confirm the cause. Here's how:

Step 1: Check Business Support Home

1. Go to Meta Business Suite or Business Manager
2. Click All Tools in the left menu
3. Select Business Support Home
4. Look under Account Overview

If you see a listed policy violation here with details about what was flagged, you're dealing with Cause 1. Meta will show you the specific policy that was breached, examples of what's allowed and not allowed, and whether an appeal is available.

If nothing shows up here — no violation, no warning, the account looks clean — you're most likely dealing with Cause 2 (the PIN/verification mismatch).

💡 If you use a BSP or WhatsApp API platform: Ask your provider to run a Health Status check on your WABA. This API endpoint often surfaces the specific reason for the lock in plain language, which is much faster than navigating Business Manager yourself.

Step-by-Step Resolution Guide

Path A: Fixing a Policy Violation

Step 1: Read the violation details carefully

In Business Support Home, click on the violation to see the full details. Meta provides a summary of which policy was breached and what content triggered it. Read this thoroughly before doing anything else.

Step 2: Fix the underlying issue

Depending on what was flagged, this could mean:

• Updating your business profile — add a working website URL, complete your business description, and make sure all details are accurate in WhatsApp Manager
• Completing business verification — go to Security Center in Business Manager and upload your official business documents if verification is still pending
• Reviewing your message templates — check that each template is correctly categorized (marketing, utility, or authentication) and that the content matches the category
• Reviewing your opt-in process — make sure everyone you're messaging has explicitly agreed to receive messages from your business via WhatsApp
• Pausing campaigns — if you were running bulk messaging campaigns, pause them until the account is reinstated

Step 3: Submit an appeal (if eligible)

Not every violation can be appealed, but many can. Here's the process:

1. From Business Support Home, select the relevant violation
2. Click Request Review
3. A dialog box opens — write a clear, factual explanation of why your business is compliant and what steps you've taken to fix the issue
4. Click Submit

The appeal moves to an "In Review" status. Meta typically responds within 24 to 48 hours with a decision: either the violation is Reversed (account unlocked) or it stays Unchanged (you may need to wait or try again after making further corrections).

Follow the steps to resolve issues using request a review in Meta Business Support Home.

⚠️ Important: Some spam-related violations are not appealable. In those cases, you may need to wait until the restriction period ends. This is another reason why catching warnings early — before they escalate to a lock — matters a lot.

Path B: Fixing a Two-Step PIN / Verification Mismatch

This is a quicker fix and doesn't involve appeals. The process is:

1. Disable two-step verification on the affected phone number (via the WhatsApp Manager or your BSP's dashboard)
2. Re-register the phone number through the API or your platform
3. Set up a new two-step verification PIN that you document carefully for future use

Make sure the PIN being submitted in any registration or verification API calls matches the PIN set on the account. A mismatch — even by one digit — will trigger this lock.

If you're not technical, ask your WhatsApp API provider or BSP to walk through this for you. Most providers can handle this process on your behalf.

Path C: Still Locked After All of the Above?

If you've checked Business Support Home (nothing flagged), you've reset the PIN, and the account is still locked:

1. Open a support ticket with Meta via Direct Support
2. In your ticket, include:

• Your WABA ID (WhatsApp Business Account ID)
• The phone number affected
• The error code: 131031
• A description of what steps you've already tried

1. If you use a BSP or API platform: Ask them to escalate on your behalf. Established BSPs often have a direct support channel with Meta and can get locks reviewed faster than going through general support.

How to Prevent This From Happening Again

Once your account is back online, a few habits will significantly reduce the risk of hitting this error again.

Keep your business profile complete and accurate. A missing website URL is one of the most common reasons Meta flags accounts. Make sure your WhatsApp Business profile has a valid URL, a clear business description, and an accurate business category.

Only message people who have opted in. WhatsApp takes user consent very seriously. Every person you message should have explicitly agreed to receive WhatsApp messages from your business — and you should be able to document that consent.

Use templates correctly. A utility template should be used for utility messages (order confirmations, delivery updates, support replies). Using it to send promotional content is a policy violation that gets caught.

Watch your quality rating. In WhatsApp Manager, keep an eye on your phone number's quality rating. A drop from Green to Yellow or Red is an early warning sign that users are reporting or blocking your messages — and it's often a precursor to a lock.

Store your 2-step PIN securely. Treat it like a password. Keep it documented in your team's password manager so you don't end up with a mismatch during future setup changes.

Set up webhook notifications. If you're on the WhatsApp Cloud API, subscribe to account_update webhook events. Meta sends real-time alerts whenever a policy issue is flagged, giving you the chance to act before it escalates to a lock.

Quick Reference: Error 131031 at a Glance

Still Struggling? We Can Help

Navigating Meta's policies and unlocking a WABA can feel overwhelming, especially when your customer communications are completely down. That's where having the right WhatsApp API platform makes all the difference — not just in sending messages, but in monitoring account health, flagging warnings before they escalate, and helping you stay compliant every step of the way.

If you're dealing with error 131031 right now, reach out to our support team and we'll help you identify the cause and get your account back online as fast as possible.

And if you're evaluating WhatsApp API providers, we'd love to show you how we make this kind of situation easier to handle — and rarer to begin with.

Sources: Meta WhatsApp Cloud API Error Code Reference | WhatsApp Business Platform Policy Enforcement Guide