Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 130403: Business has blocked the user

Error 130403 is the one delivery failure your own team causes on purpose: the business number has blocked this WhatsApp user, so WhatsApp won't deliver messages from you to them until the block is lifted.

130403
Code
Business has blocked the user
Meta's name
Delivery
Type
API response or failure webhook
Where you see it
No, don't resend
Retry

Quick answer

Your business blocked this customer. If that was intended, stop messaging them; if not, unblock the user and then send again.

What WhatsApp error 130403 means

Meta documents 130403 as: unable to deliver the message because this business has blocked the end user on WhatsApp. It advises against retrying and says to unblock the user to resume sending. The block is a business-side action, usually taken to stop abusive or spam messages from that person.

Why error 130403 happens

The message itself was fine; something about the recipient or your relationship with them stopped it. Typical triggers:

  • An agent blocked an abusive or spamming contact and the contact is still in a campaign list.
  • An automation blocks users after repeated off-topic messages and later tries to send them an order update.
  • A block was applied to the wrong contact by mistake.

How to fix error 130403

There is no request change that gets this message delivered; the work is in your data and your audience.

  • Check whether the block was deliberate and who applied it.
  • If it was deliberate, remove the contact from active audiences so no further sends are attempted.
  • If it was a mistake or the issue is resolved, unblock the user, then send the message again.
  • Note that a blocked user can't message you either: if a customer says their messages aren't reaching you, check your block list.

Should you retry after 130403?

Do not retry while the block is in place; every attempt will fail the same way. Retry only after the user has been unblocked.

How error 130403 shows up in InfiQ

If Meta rejects the send straight away, InfiQ's API answers with an HTTP error that carries Meta's own error object: error.code 130403, a message beginning "(#130403)" and Meta's explanation in error_data.details, plus an InfiQ_traceid. If Meta accepts the message and it fails afterwards, InfiQ posts a message.failed webhook for it with metaErrorCode 130403, linked to the message by its ID and wamid. 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.

Send it through InfiQ

Frequently asked questions

Is error 130403 the same as the customer blocking my business?+
No. 130403 is returned when your business has blocked the user. When a customer blocks or reports your number, the effect shows up differently, for example as a lower quality rating or delivery failures such as 131026, not as 130403.
Does unblocking a user restart the conversation?+
Unblocking only lifts the restriction. To message the person again outside an open 24-hour customer service window you still need an approved template.