Code

Description

Possible Solutions

HTTP Status Code

0

AuthException

We were unable to authenticate the app user.

Typically this means the included access token has expired, been invalidated, or the app user has changed a setting to prevent all apps from accessing their data. We recommend that you get a new access token.

401

Unauthorized

3

API Method

Capability or permissions issue.

Use the access token debugger to verify that your app has been granted the permissions required by the endpoint. See Troubleshooting.

500

Internal Server Error

10

Permission Denied

Permission is either not granted or has been removed.

Use the access token debugger to verify that your app has been granted the permissions required by the endpoint. See Troubleshooting.

Ensure that the phone number used to set the business public key is allowlisted.

403

Forbidden

190

Access token has expired

Your access token has expired.

Get a new access token.

401

Unauthorized

200-299

API Permission

Permission is either not granted or has been removed.

Use the access token debugger to verify that your app has been granted the permissions required by the endpoint. See Troubleshooting.

403

Forbidden

Code

Description

Possible Solutions

HTTP Status Code

4

API Too Many Calls

The app has reached its API call rate limit.

Load the app in the App Dashboard and view the Application Rate Limit section to verify that the app has reached its rate limit. If it has, try again later or reduce the frequency or amount of API queries the app is making.

400

Bad Request

80007

Rate limit issues

The WhatsApp Business Account has reached its rate limit.

See WhatsApp Business Account Rate Limits. Try again later or reduce the frequency or amount of API queries the app is making.

400

Bad Request

130429

Rate limit hit

Cloud API message throughput has been reached.

The app has reached the API's throughput limit. See Throughput. Try again later or reduce the frequency with which the app sends messages.

400

Bad Request

131048

Spam rate limit hit

Message failed to send because there are restrictions on how many messages can be sent from this phone number. This may be because too many previous messages were blocked or flagged as spam.

Check your quality status in the WhatsApp Manager and see the Quality-Based Rate Limits documentation for more information.

400

Bad Request

131049

Meta chose not to deliver.

This message was not delivered to maintain healthy ecosystem engagement.

Do not retry immediately if you do receive this error code and suspect it is due to the limit. Instead, retry in increasing larger time increments until the message is delivered, since the limit may be in effect for differing periods of time.

See Per-User Marketing Template Message Limits for additional information.

400

Bad Request

131056

(Business Account, Consumer Account) pair rate limit hit

Too many messages sent from the sender phone number to the same recipient phone number in a short period of time.

Wait and retry the operation, if you intend to send messages to the same phone number. You can still send messages to a different phone number without waiting

400

Bad Request

133016

Account register deregister rate limit exceeded

Registration or Deregistration failed because there were too many attempts for this phone number in a short period of time

The business phone number is being blocked because it has reached its registration/deregistration attempt limit. Try again once the number is unblocked. See "Limitations" in the Registration document.

400

Bad Request

Code

Description

Possible Solutions

HTTP Status Code

368

Temporarily blocked for policies violations

The WhatsApp Business Account associated with the app has been restricted or disabled for violating a platform policy.

See the Policy Enforcement document to learn about policy violations and how to resolve them.

403

Forbidden

131031

Account has been locked

The WhatsApp Business Account associated with the app has been restricted or disabled for violating a platform policy, or we were unable to verify data included in the request against data set on the WhatsApp Business Account (e.g, the two-step pin included in the request is incorrect).

See the Policy Enforcement document to learn about policy violations and how to resolve them.

You can also use the Health Status API, which may provide additional insight into the reason or reasons for the account lock.

403

Forbidden

Code

Description

Possible Solutions

HTTP Status Code

1

API Unknown

Invalid request or possible server error.

Check the WhatsApp Business Platform Status page to see API status information. If there are no server outages, check the endpoint reference and verify that your request is formatted correctly and meets all endpoint requirements.

400

Bad Request

2

API Service

Temporary due to downtime or due to being overloaded.

Check the WhatsApp Business Platform Status page to see API status information before trying again.

503

Service Unavailable

33

Parameter value is not valid

The business phone number has been deleted.

Verify that the business phone number is correct.

400

Bad Request

100

Invalid parameter

The request included one or more unsupported or misspelled parameters.

See the endpoint's reference to determine which parameters are supported and how they are spelled.

Ensure when setting the business public key, it is a valid 2048-bit RSA public key in PEM format.

Ensure there is no mismatch between the phone number id you are registering and a previously stored phone number id.

400

Bad Request

130472

User's number is part of an experiment

Message was not sent as part of an experiment.

See Marketing Message Experiment.

400

Bad Request

131000

Something went wrong

Message failed to send due to an unknown error.

When setting a business public key, it either failed to calculate the signature, call the GraphQL endpoint, or the GraphQL endpoint returned an error.

Try again. If the error persists, open a Direct Support ticket.

500

Internal Server Error

131005

Access denied

Permission is either not granted or has been removed.

Use the access token debugger to verify that your app has been granted the permissions required by the endpoint. See Troubleshooting.

403

Forbidden

131008

Required parameter is missing

The request is missing a required parameter.

See the endpoint's reference to determine which parameters are required.

400

Bad Request

131009

Parameter value is not valid

One or more parameter values are invalid.

See the endpoint's reference to determine which values are supported for each parameter, and see Phone Numbers to learn how to add a phone number to a WhatsApp Business Account.

400

Bad Request

131016

Service unavailable

A service is temporarily unavailable.

Check the WhatsApp Business Platform Status page to see API status information before trying again.

500

Internal Server Error

131021

Recipient cannot be sender

Sender and recipient phone number is the same.

Send a message to a phone number different from the sender.

400

Bad Request

131026

Message Undeliverable

Unable to deliver message. Reasons can include:

• The recipient phone number is not a WhatsApp phone number.

• Sending an authentication template to a WhatsApp user who has a +91 country calling code (India). Authentication templates currently cannot be sent to WhatsApp users in India.

• Recipient has not accepted our new Terms of Service and Privacy Policy.

• Recipient using an old WhatsApp version; must use the following WhatsApp version or greater:

• Android: 2.21.15.15

• SMBA: 2.21.15.15

• iOS: 2.21.170.4

• SMBI: 2.21.170.4

• KaiOS: 2.2130.10

• Web: 2.2132.6

• The message was not delivered to create a high quality user experience. See Per-User Marketing Template Message Limits.

Using a non-WhatsApp communication method, ask the WhatsApp user to:

• Confirm that they can actually send a message to your WhatsApp business phone number.

• Confirm that they have accepted our latest Terms of Service (Settings > Help, or Settings > Application information will prompt them to accept the latest terms/policies if they haven't done so already)

• Update to the latest version of the WhatsApp client.

400

Bad Request

131042

Business eligibility payment issue

There was an error related to your payment method.

See About Billing For Your WhatsApp Business Account and verify that you have set up billing correctly.

Common problems:

• Payment account is not attached to a WhatsApp Business Account

• Credit line is over the limit

• Credit line (Payment Account) not set or active

• WhatsApp Business Account is deleted

• WhatsApp Business Account is suspended

• Timezone not set

• Currency not set

• MessagingFor request (On Behalf Of) is pending or declined

• Exceeded conversation free tier threshold without a valid payment method

400

Bad Request

131045

Incorrect certificate

Message failed to send due to a phone number registration error.

Register the phone number before trying again

500

Internal Server Error

131047

Re-engagement message

More than 24 hours have passed since the recipient last replied to the sender number.

Send the recipient a business-initiated message using a message template instead.

400

Bad Request

131051

Unsupported message type

Unsupported message type.

See Messages for supported message types before trying again with a supported message type.

400

Bad Request

131052

Media download error

Unable to download the media sent by the user.

We were unable to download the media for one or more reasons, such as an unsupported media type. Refer to the error.error_data.details value for more information about why we were unable to download the media.

Ask the WhatsApp user to send you the media file using a non-WhatsApp method.

400

Bad Request

131053

Media upload error

Unable to upload the media used in the message.

We were unable to upload the media for one or more reasons, such as an unsupported media type. Refer to the error.error_data.details value for more information about why we were unable to upload the media.

We recommend that you inspect any media files that are causing errors and confirm that they are in fact supported.

For example, in UNIX you can use file inspection via the command line to determine its MIME type:

file -I rejected-file.mov

You can then confirm if its MIME type is listed in our list of supported media types.

For more reliable performance when sending media, refer to Media HTTP Caching and uploading the media.

400

Bad Request