Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 131031: Account has been locked

Error 131031 means the WhatsApp Business Account is locked. Meta returns it for two quite different reasons: a policy restriction on the account, or data in your request that doesn't match what's set on the account.

131031
Code
Account has been locked
Meta's name
Account enforcement
Type
On the API response
Where you see it
After fixing the cause
Retry

Quick answer

The account is locked, either for a policy violation or because something in the request, such as the two-step verification PIN, doesn't match the account. Check the account's health status to see which.

What WhatsApp error 131031 means

Meta documents 131031 as an integrity error: the account has been restricted or disabled for violating a platform policy, or Meta couldn't verify data in the request against data set on the account, for example an incorrect two-step PIN. Meta suggests its health status endpoint for more insight into why the account is locked.

Why error 131031 happens

Enforcement errors follow from how the account has been used. They usually trace back to one of these:

  • A policy violation that led Meta to lock the account.
  • A two-step verification PIN in a registration request that doesn't match the one set on the number.
  • Other request data that doesn't match the account's settings.

How to fix error 131031

Work through these in order; the first one that turns up a problem is usually the fix.

  • Check the account's health status and its policy notices to see whether it's an enforcement lock.
  • If it's an enforcement lock, treat it like error 368: fix the cause and request a review.
  • If it came from registration, confirm the two-step PIN; reset it from WhatsApp Manager if nobody knows it.
  • Resend once the lock is lifted or the data matches.

Should you retry after 131031?

Don't retry blindly. A PIN mismatch is fixed by sending the right PIN; an enforcement lock needs the account to be reviewed or the restriction to end.

How error 131031 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 131031, a message beginning "(#131031)" and Meta's explanation in error_data.details, plus an InfiQ_traceid. Keep the trace IDs with the failed message: they are what support needs to look it up.

Send it through InfiQ

Frequently asked questions

How do I know if error 131031 is a policy lock?+
Check the account's health status and the policy notices for the account. A policy lock shows up there with the reason; a PIN or data mismatch does not.
Does error 131031 affect every number in the account?+
An enforcement lock applies to the WhatsApp Business Account, so yes. A PIN or data mismatch only affects the request that carried it, such as the registration of one number.