WhatsApp error 131048 (spam rate limit hit): why Meta restricted your number and how to recover

WhatsApp error 131048 means Meta is limiting how many messages your phone number can send right now. Meta's error reference says: "Message failed to send because there are restrictions on how many messages can be sent from this phone number. This may be because too many previous messages were blocked or flagged as spam." Its suggested fix is: "Check your quality status in the WhatsApp Manager," and it points to Meta's pages on template limits and template quality. Unlike most send errors, this one is a judgement about what your number has been sending recently.

How 131048 differs from other limits

Several WhatsApp errors sound like "too many messages". They have different causes, and treating one like another is the most common mistake:

Your messaging limit tier (250, 2,000, 10,000, 100,000 or unlimited unique users in a rolling 24 hours) is yet another control. A healthy number can be well inside its tier and still hit 131048 if a recent send drew a wave of blocks.

Why it happens

The signal Meta names is blocks and spam reports. In Indian campaigns these usually come from:

• Lists without real opt-in: numbers from a database purchase, a scraped directory, or a WhatsApp group export.
• Stale numbers: enquiries from a fair or a lead form many months ago, where people no longer remember the business.
• Volume spikes: a number that sent a few hundred messages a day suddenly sends to its whole tier for a sale.
• Repetition: the same promotional template several times in a week.
• Unclear sender: a display name or opening line that does not make the business obvious, so the message looks like spam.

What the error looks like

131048 can come back on the send request or in the failed-status webhook. Illustrative webhook (title and details wording vary):

{
  "statuses": [
    {
      "id": "wamid.HBgMOTE5OTI4MDA1NTQzFQIAERgSRjhB...",
      "status": "failed",
      "timestamp": "1761990600",
      "recipient_id": "919928005543",
      "errors": [
        {
          "code": 131048,
          "title": "Spam rate limit hit",
          "message": "Spam rate limit hit",
          "error_data": {
            "details": "Message failed to send because there are restrictions on how many messages can be sent from this phone number."
          }
        }
      ]
    }
  ]
}

If you see this code for many recipients in the same minute, treat it as a number-level event, not a list of bad contacts.

Step-by-step recovery

1. Stop every bulk send from the number. Pause campaigns and broadcast jobs. Leave replies to customers who message you, which are the healthiest traffic you have.
2. Check quality in WhatsApp Manager. Look at the phone number's quality rating and at each template's quality. A template that is low quality or paused (error 132015) tells you which message drew the blocks.
3. Find the send that caused it. Line up the last few days of campaigns with the time 131048 started. Note the template, the list source and the volume.
4. Cut the audience. Remove numbers with no opt-in record, numbers that never read a message, and contacts who opted out by any route.
5. Fix the message. Name the business in the first line, keep one clear offer, and add an opt-out quick reply.
6. Restart small and watch. Send to your most engaged customers first, then widen in steps over several days while the quality rating stays healthy. Meta does not publish how long the restriction lasts, so watch whether sends succeed rather than counting hours.

A worked example

Arjun manages WhatsApp for a furniture store in Lucknow. Ahead of a sale he uploads 4,500 numbers: 1,200 recent buyers and 3,300 numbers bought from a local data seller. The campaign starts well, then a growing share of sends fails with 131048 and the template's quality turns low (illustrative pattern).

He stops the campaign and deletes the purchased numbers from the CRM rather than just excluding them. Two days later he resumes only to the recent buyers, with a reworded message that opens "Hi Priya, this is Sharma Furniture, Hazratganj" and ends with a "Stop offers" button, at a few hundred messages a day. For new reach he switches to Click-to-WhatsApp ads, where customers start the chat themselves.

Preventing 131048

• Send only to people who opted in to messages from your named business, and keep the record of where and when.
• Grow volume gradually instead of jumping to the top of your tier on sale day.
• Segment by recency and engagement; retire contacts who never read.
• Offer an easy opt-out in every marketing template and honour it everywhere.
• Watch quality daily during a campaign, not after it ends.

How Broadchat responds to 131048

Broadchat's Meta client does not retry 131048 automatically. In a campaign, a recipient whose send fails with this code is marked failed with Meta's message, and message info shows the reason "Spam rate limit hit — the number sent too many messages that were blocked or reported." with code 131048. The channel card shows the number's quality rating and messaging limit as Meta reports them, so you can watch recovery without opening WhatsApp Manager. Campaign reports can be exported as CSV, which makes it easy to split results by list source as in the example above. Pausing the campaign is your decision; Broadchat does not change your audience for you.

The background on limits is in WhatsApp messaging limits and tiers and how quality rating affects messaging limits. For list hygiene, read WhatsApp opt-in best practices, and for every other code the WhatsApp API error codes cheat-sheet.