WhatsApp Cloud API · error code

WhatsApp error 131050: User has stopped reciept of marketing messages.

Permanent - do not retryHTTP 400Recipient & delivery

Last verified against Meta for Developers - Cloud API error codes

What WhatsApp returns
Unable to deliver the message. This recipient has chosen to stop receiving marketing messages on WhatsApp from your business.

What error 131050 means

Code 131050 means the recipient has used WhatsApp's built-in control to stop receiving marketing messages from your business specifically. This is a user preference enforced by the platform, not a block: the person can still message you, still receive your utility and authentication templates, and still get your replies inside the service window. Only marketing templates are refused, and they are refused with 131050 until the user opts back in.

Meta is explicit that you should not retry. The message will not be delivered while the preference stands. The platform provides a user_preferences webhook that notifies you whenever a user stops or resumes marketing messages from your business, which is the mechanism intended to keep your own suppression list accurate.

Your account quality is not being penalized by this error itself, but continuing to attempt marketing sends to users who opted out is the kind of behaviour that eventually does affect quality.

Why it happens

  • The user tapped the option to stop marketing messages from your business on a previous marketing template.
  • Your suppression list is not synchronized with the user_preferences webhook, so opted-out users remain in campaigns.
  • A campaign imported an audience from another system that does not carry WhatsApp opt-out state.
  • Content categorized as marketing being sent to someone who only expects transactional messages.

How to fix WhatsApp error 131050

  1. 1Stop retrying this message; it will not be delivered.
  2. 2Mark the contact as opted out of WhatsApp marketing in your CRM immediately.
  3. 3Subscribe your app to the user_preferences webhook field and process stop and resume events into your suppression list.
  4. 4If the content is transactional, send it as a utility template instead, which is still permitted.
  5. 5Audit recent campaigns for other 131050 responses and suppress those contacts too.

How to stop it recurring

Treat the user_preferences webhook as authoritative and wire it into your audience system so opted-out users are excluded before dispatch. Keep marketing and utility templates clearly separated so a user who opts out of marketing still receives what they need. Report opt-outs per campaign; a rising rate is feedback about content and frequency. Like other delivery-time failures it arrives in the statuses webhook, so a broken webhook pipeline hides opt-outs from you - worth ruling out with the webhook debugging guide. The platform-enforced drop for frequency rather than preference is 131049.

Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.

Related codes

Error 131050 - quick answers

What does WhatsApp error 131050 mean?

Code 131050 means the recipient has used WhatsApp's built-in control to stop receiving marketing messages from your business specifically. This is a user preference enforced by the platform, not a block: the person can still message you, still receive your utility and authentication templates, and still get your replies inside the service window.

How do I fix WhatsApp error 131050?

1. Stop retrying this message; it will not be delivered. 2. Mark the contact as opted out of WhatsApp marketing in your CRM immediately. 3. Subscribe your app to the user_preferences webhook field and process stop and resume events into your suppression list. 4. If the content is transactional, send it as a utility template instead, which is still permitted. 5. Audit recent campaigns for other 131050 responses and suppress those contacts too.

Should I retry after error 131050?

No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.

Stop debugging WhatsApp by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.