Error 131048 is the error most often blamed on volume and almost never caused by it. Meta documents it as "Spam rate limit hit," noting restrictions on message volume from this phone number, with an HTTP status of 400 and a recommended action of checking quality status in WhatsApp Manager and reviewing template quality metrics (Meta for Developers, WhatsApp error codes reference, retrieved 2026-08-17).
That recommended action is the tell. Meta does not send you to your rate limits or your tier; it sends you to your quality status. Error 131048 is a consequence of what recipients did with your previous messages, not of how many you tried to send. Teams that respond by slowing their send rate see the error persist, because throttling the same content to the same unhappy audience changes nothing.
This guide covers what actually triggers 131048, how it differs from the other throttling codes it gets confused with, how recovery works, and what to fix so it does not return. For the wider failure surface, our WhatsApp Business API error codes reference indexes the rest.
What Triggers Error 131048
The mechanism is straightforward once you stop thinking about it as a rate limit in the usual sense.
WhatsApp measures how recipients respond to your messages. Blocks and spam reports are the strongest negative signals, and they feed the quality rating on the phone number that sent them. Quality rating is assessed on recent user feedback, described by BSP documentation as based on user response over the last 24 hours (Turn.io, retrieved 2026-08-17). When those signals cross a threshold, WhatsApp restricts what that number can send.
The practical triggers, in rough order of how often they appear:
Messaging contacts with weak or absent consent. A list imported from another channel, an old database, or a purchased source. Recipients do not recognise the sender and block it. This is the dominant cause and no amount of throttling addresses it.
Frequency that outpaces relevance. Contacts who did opt in, receiving more than they expected or wanted. Blocks from formerly engaged users are the clearest signal you have crossed this line.
Content that reads as promotional in a channel users treat as personal. WhatsApp sits alongside messages from family. Copy that would be unremarkable in email can feel intrusive here.
Sending to cold segments to hit a number. Campaigns sized to a target rather than to genuine engagement, which mixes engaged contacts with dormant ones and pulls the signal down.
What does not trigger it: high volume to an engaged, properly opted-in audience. Businesses at very high daily volumes maintain high quality ratings routinely. Volume amplifies your consent quality in both directions; it does not set it.
How 131048 Differs From the Other Throttling Codes
Four codes get treated interchangeably and mean quite different things. Diagnosing correctly determines whether you fix code or fix marketing.
Code | What it means | Scope | What actually fixes it |
|---|---|---|---|
4 | App-level API rate limit reached | Your app | Backoff and request pacing |
131048 | Spam rate limit from quality signals | One phone number | Improve consent, relevance, frequency |
131056 | Per-recipient pair rate limit | One sender/recipient pair | Stop messaging that contact so frequently |
131064 | Messaging limit reduced for template classification violations | Account | Categorise templates honestly |
130429 | Throughput limit | Your number's throughput | Request higher throughput; pace sends |
If you are hitting error 4 or 130429, engineering can fix it with pacing and backoff. If you are hitting 131048 or 131064, engineering cannot fix it at all, because the constraint is downstream of a marketing decision. Our guides to WhatsApp API rate limits and messaging limits cover the mechanical limits in detail.
What to Do When You Hit It
1. Stop the campaign that is running. Not slow it. Stop it. Every further message to the same segment adds negative signal to the number that is already restricted.
2. Check quality status per number in WhatsApp Manager. This is Meta's recommended action. Look at the rating on the restricted number specifically, since businesses running several numbers often find the problem isolated to one.
3. Review template-level quality metrics. Meta's action also names template quality. Frequently one template is generating most of the negativity while others perform fine. Identify it before you change anything broadly.
4. Segment by engagement and confirm consent. Split your recent send audience by whether they have ever replied or interacted, and by how and when they opted in. The gap between those groups is usually where the blocks came from.
5. Resume narrowly. Restart with your most engaged, most clearly opted-in segment and your best-performing template. Volume can return once the signals have; leading with volume restarts the cycle.
An operational note on 2026 behaviour, because most published guidance is stale here. The "Flagged" phone number status has been removed, and messaging limits no longer automatically decrease when quality rating drops (respond.io, Turn.io, both retrieved 2026-08-17). Meta's current messaging-limits documentation likewise does not describe an automatic downgrade path. This matters for 131048 specifically: the intermediate visible warning that many teams used as a canary is gone, so the spam rate limit may be the first hard consequence you see. Quality rating needs to be monitored directly rather than inferred from limit changes.
Preventing a Repeat
The fix for 131048 is a list-quality fix, and it sits with whoever owns lifecycle marketing rather than whoever owns the integration.
Record consent per contact, specific to WhatsApp. Where, when, and how. Consent collected for email is not consent for WhatsApp. If you cannot produce the record for a segment, that segment is a liability regardless of its open rate. Our WhatsApp opt-in guide covers what Meta expects.
Cap frequency yourself, below what Meta enforces. Meta applies per-user marketing limits through error 131049, but the enforced ceiling is not a target. Set your own cap based on engagement and hold to it.
Suppress aggressively. Contacts who never engage, and numbers that repeatedly fail with error 131026, should leave your active list. Sending to them cannot produce revenue and can produce blocks.
Separate transactional from promotional numbers. Running order notifications and marketing campaigns from different phone numbers means a marketing quality problem cannot throttle your order confirmations. For businesses where transactional delivery is critical, this is the highest-value structural change available, and our guide to multiple numbers on one WhatsApp Business Account covers the setup.
Give quality rating an owner and an alert. Not a dashboard someone checks occasionally. A named owner, an alert on any drop from high, and the authority to stop a campaign. Because the automatic limit-decrease warning no longer exists, this is now the only reliable early signal.
Worth being direct about the framing: 131048 is usually reported to engineering as a throttling bug and it is not one. The platform is relaying, accurately, that a measurable share of recipients did not want the message. Treating it as an infrastructure problem to be tuned around is what produces a second 131048 and eventually a 368. Our guide on WhatsApp marketing mistakes covers the practices that generate these signals.
Frequently Asked Questions
What causes WhatsApp error 131048?
Blocks and spam reports from recipients, which lower the quality rating on the sending phone number until WhatsApp restricts its message volume. Meta's recommended action is to check quality status in WhatsApp Manager and review template quality metrics, which confirms the cause is recipient response rather than send volume.
Does reducing my send volume fix error 131048?
Not by itself. Reducing volume slows the accumulation of negative signals but does not improve them, so the restriction tends to persist or return. What resolves it is sending to contacts with genuine WhatsApp consent, at a frequency they tolerate, with content they find useful. Volume can safely return once the quality signals have recovered.
How long does the spam rate limit last?
Meta does not publish a fixed duration, because recovery depends on your quality signals improving rather than on elapsed time. Quality rating is assessed on recent user feedback, so improvement can appear within days if the underlying practice changes, and not at all if it does not.
Is error 131048 the same as a rate limit?
No, despite the name. Error 4 and 130429 are mechanical rate and throughput limits that engineering resolves with pacing and backoff. Error 131048 is a quality-driven restriction that pacing cannot resolve, because the constraint follows from how recipients responded to previous messages.
Does error 131048 affect my whole WhatsApp Business Account?
No. It restricts the specific phone number that generated the negative signals. That is what distinguishes it from error 368, which is an account-level restriction stopping every number on the WABA. Running separate numbers for transactional and promotional traffic contains the blast radius.
Will I get a warning before hitting the spam rate limit?
Less reliably than in the past. Independent BSP documentation states that the Flagged status has been removed and that messaging limits no longer automatically decrease when quality rating drops, which removed an intermediate warning many teams relied on. Monitor quality rating directly, with an alert on any drop from high.
The Constraint Is the Audience, Not the Pipe
Error 131048 is WhatsApp reporting a marketing measurement through an engineering channel, which is why it so often gets tuned instead of fixed. The number was restricted because recipients blocked or reported it, and no amount of pacing, retry logic, or throughput negotiation changes that input.
The teams that clear 131048 and never see it again do two things: they can produce a per-contact WhatsApp consent record for every segment they message, and they cap frequency below what Meta would enforce. The teams that see it repeatedly are usually the ones still treating the enforced ceiling as the target.
Want quality monitored before it becomes a restriction? Helo.ai is a Meta Partner and tracks per-number quality rating, template quality, and engagement segmentation for enterprise programmes, with alerting that fires before throughput is cut. Talk to an expert.
Next: error 131049 for the per-user marketing frequency limit, or error 131064 if your restriction traces to template categorisation.
