WhatsApp API error 131048: Spam rate limit hit
Error 131048 is Meta telling you that your business number has been sending messages people don't want. Too many recipients blocked the number or reported it as spam, so WhatsApp is holding back how many messages it will accept from that number for now.
Quick answer
Your number is being rate-limited because recent messages were blocked or reported as spam. Stop the campaign, fix who you send to and what you send, and let the number's quality recover before sending at volume again.What WhatsApp error 131048 means
Meta documents 131048 as a throttling error: the message failed because of restrictions on how many messages can be sent from this phone number, most likely because too many earlier messages were blocked or flagged as spam. It is a judgement about your recent sending, not about the message in hand, so the same template can go through fine from a healthy number.
Why error 131048 happens
Limits like this are triggered by sending patterns rather than single messages. The patterns that usually cause it:
- A broadcast went to a list that never opted in, or opted in long ago for something else.
- Several marketing templates went to the same people within a few days, and they started blocking the number.
- The content looked like spam to recipients: vague offers, no clear sender, no way to stop.
- A newly imported or purchased contact list, with many people who don't recognise the business.
- The number's quality rating had already dropped to low and the warning was missed.
How to fix error 131048
Recovery takes time, so the aim is to stop making it worse and fix the cause meanwhile.
- Pause every bulk send from the affected number at once; each further block deepens the restriction.
- Check the number's quality rating and any notices in WhatsApp Manager to see how far it has fallen.
- Cut the audience back to people who opted in recently and specifically to WhatsApp messages from you.
- Rewrite the template so the sender, the reason for the message and the way to opt out are obvious, and add a quick-reply opt-out button.
- Restart slowly with smaller batches to your most engaged contacts, and watch blocks and replies before scaling up.
Should you retry after 131048?
Retrying straight away makes it worse: every message that fails or gets blocked keeps the restriction in place. Wait until the quality rating has recovered, then resume with a smaller, better-targeted audience. Transactional messages to customers who are expecting them are the safest way to rebuild trust.
How error 131048 shows up in InfiQ
When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 131048, the "(#131048)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. When the failure only shows up after the send was accepted, it arrives as a message.failed webhook whose data.error.metaErrorCode is 131048, tied to the original message. Treat both the same way in your error handling. Keep the trace IDs with the failed message: they are what support needs to look it up. Because 131048 is about the number rather than one message, expect it on many sends at once. In InfiQ, filter your failed messages by this code to see which campaign triggered it.