circle-exclamationError Code Reference

This page provides API error codes along with possible steps for resolution.

360Dialog Messaging Errors

Code
Description / Developer message
Possible Solution

400

Your WhatsApp for Business API has been disabled

Contact support.

400

You have exceeded the endpoint rate limit.

Implement request throttling or exponential backoff to cool down API requests and avoid exceeding rate limits. Contact support.

400

Could not send message due to lack of payment. Messaging can resume once overdue invoices towards 360Dialog are settled. Please reach out to our integration partner.

Contact integration partner or support to resolve account billing issues.

401

Invalid API key

Check that the API is the correct and valid for the number you are trying to use. Generate another API key if required. Check the key value is being passed in the D360-API-KEY header.

403

The endpoint is blocked

Contact support to see if the specific endpoint can be enabled.

500

Internal server error

There are various reasons for this error. Contact support.

502

WhatsApp for Business API not available

Contact support.

360Dialog Partner API Errors

Code
Description / Developer message
Possible Solution

403

Permission denied for partner x

  • Verify the Auth token header is valid

  • Confirm the user has the necessary permissions to access this Partner Hub.

  • If the issue persists, contact 360Dialog support

Meta Cloud API Integrity Errors

The following errors are returned with a 403 - Forbidden HTTP Status Code.

Meta Error Code
Description
Possible Solutions

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 Enforcementarrow-up-right document to learn about policy violations and how to resolve them. Contact support.

130497 - Business account is restricted from messaging users in this country.

The WhatsApp Business Account is restricted from messaging to users in certain countries.

Businesses can only send messages to countries they have been specifically approved for. This error is received when a message is sent to an unauthorized country.

Cross-country messaging can be unlocked for an account by completing a scaling path to reach the 2,000 messaging limit tierarrow-up-right. It may take up to 30 days for cross-country messaging to be unlocked after completing a scaling path.

It may not be possible to send a cross-country message to recipients in Brazil and Indonesia even after a scaling path is completed. There is no known solution at this time.

If the business's activities are prohibited in other countries, messaging recipients of said countries may result in this error as well. See WhatsApp Business Messaging Policyarrow-up-right for details on allowed countries for messaging in your business category.

131031 - Account has been locked

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

  1. Disable 2FA

  2. Re-register the number

  3. Enable 2FA again

Use the healthcheck endpoint, which may provide additional insight into the reason for the account lock. See the specific guide about how to solve the 'Business account has been locked' error. If you cannot get the WABA unblocked, contact support.

Other Meta Messaging Errors

Meta Error Code
Description
Possible Solutions

1 - API Unknown

Invalid request or possible server error.

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

2- API Service

Temporary due to downtime or due to being overloaded.

Check the WhatsApp Business Platform Statusarrow-up-right page to see API status information before trying again.

130472 - User's number is part of an experiment

Message was not sent as part of an experimentarrow-up-right.

131000 - Something went wrong

Message failed to send due to an unknown error.

Try again. If the error persists, contact 360Dialog support.

131005 - Access denied

Permission is either not granted or has been removed.

Try again. If the error persists, contact 360Dialog support.

131008 - Required parameter is missing

The request is missing a required parameter.

See the endpoint's referencearrow-up-right to determine which parameters are required.

131016 - Service unavailable

A service is temporarily unavailable.

Check the WhatsApp Business Platform Statusarrow-up-right page to see API status information before trying again. If the error persists, contact 360Dialog support.

131021

Sender and recipient phone number is the same.

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

131026 - Message Undeliverable

Unable to deliver message. The following scenarios can cause a message to appear as sent but not delivered. For many of these reasons, Meta does not disclose the underlying cause of the error, due to privacy and policy reasons.

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

  • The customer has blocked the business.

  • Recipient has not accepted Meta's 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

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 your WhatsApp business phone number is not in their list of blocked numbers (Settings > Privacy > Blocked or Blocked contacts)

  • Confirm that they have accepted Meta 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

131037 - WhatsApp provided number needs display name approval before message can be sent.

The 555 business phone numberarrow-up-right used to send the request does not have an approved display namearrow-up-right.

Change the 555 business phone number's display name. See our How to change your WhatsApp Business display namearrow-up-right Help Center article to learn how.

131042 - Business eligibility payment issue

There was an error related to your payment method.

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

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. Threshold for expected behavior is ≤1% In case the error occurs more frequently, please get in touch with customer support.

131049 - Meta chose not to deliver.

This message was not delivered to maintain healthy ecosystem engagement.

If you do receive this error code and suspect it is due to the limit, wait at least 24 hours before resending the template message. Doing so will only result in another error response since the limit may be in effect for differing periods of time. See Per-User Marketing Template Message Limitsarrow-up-right for additional information. The error 131049 indicates that Meta intentionally chose not to deliver the message in order to maintain a healthy ecosystem engagement. In essence, the message was not sent to preserve the integrity of the ecosystem.

To prevent this error from occurring again, it's recommended not to attempt resending the message immediately after receiving this error. Instead, you should try sending the message at progressively longer intervals until it is successfully delivered, as the duration of the imposed limit can vary. Wait at least 24 hours before resending the template message.

This feature is deployed for all businesses, (even businesses with OBA) and there is no whitelisting list available. This limit is not active in these countries: European Economic Area, United Kingdom, Japan, South Korea

As mentioned in the Meta developer documentationarrow-up-right:

"WhatsApp has found that per-user marketing template limits maximize marketing message engagement and improve the user experience, measured through improvements in user read rates and sentiment. This limit helps WhatsApp users find business messaging more valuable and feel less like they receive too many business messages.

Our per user marketing limit adapts automatically over time based on a person’s recent engagement levels. While this may mean delivering fewer messages to some users during periods of lower marketing read rates or overall inbox activity, rest assured your ability to reach people when they are most engaged will not change."

131051 - Unsupported message type

Unsupported message type.

See Messagesarrow-up-right for supported message types before trying again with a supported message type.

131052 - Media download error

Unable to download the media sent by the user.

We were unable to download media included in the WhatsApp user's message. For more information, refer to the error.error_data.details value in any messages webhooks triggered when this message was received.

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

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.

For more information, refer to the error.error_data.details value in any messages webhooks triggered when this message fails to send.

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 supported. See Supported Media Typesarrow-up-right.

131057 - Account in maintenance mode

Buiness Account is in maintenance mode

The WhatsApp Business Account is in maintenance mode. One reason for this could be that the account is undergoing a throughput upgrade.

132000 - Template Param Count Mismatch

The number of variable parameter values included in the request did not match the number of variable parameters defined in the template.

See Message Template Guidelinesarrow-up-right and make sure the request includes all of the variable parameter values that have been defined in the template.

132001 - Template does not exist

The template does not exist in the specified language or the template has not been approved.

Make sure your template has been approved and the template name and language locale are correct. Please ensure you follow message template guidelinesarrow-up-right.

132005 - Template Hydrated Text Too Long

Translated text is too long.

Check the WhatsApp Manager to verify that your template has been translated. See Quality Rating and Template Statusarrow-up-right.

132007 - Template Format Character Policy Violated

Template content violates a WhatsApp policy.

See Rejection Reasonsarrow-up-right to determine possible reasons for violation.

132012 - Template Parameter Format Mismatch

Variable parameter values formatted incorrectly.

The variable parameter values included in the request are not using the format specified in the template. See Message Template Guidelinesarrow-up-right.

135000 - Generic user error

Message failed to send because of an unknown error with your request parameters.

The error you encountered was related to template restrictions, which are in place due to Meta security concerns. Unfortunately, Meta will disclose further details about these restrictions. Contact 360Dialog support

Meta Number Registration Errors

Code
Description
Possible Solution
HTTP Status Code

1005 - Timeout

Registration timeout

Wait until the timeout phase has lapsed and try again.

403 - Forbidden

1005 - Unknown error: biz_link_info_invalid_payload

The WhatsApp personal app or WhatsApp Business app account was not deleted.

Reinstall WhatsApp or WhatsApp Business and then fully deletearrow-up-right it. This will allow the number to be registered for the WhatsApp Business API.

403 - Forbidden

1005 - This number has not been approved for an enterprise

The WhatsApp App or WhatsApp Business App account was not deleted.

Reinstall WhatsApp or WhatsApp Business and then fully deletearrow-up-right it. This will allow the number to be registered for the WhatsApp Business API.

403 - Forbidden

1005 - There was an error verifying this phone number

This means that the registration has been locked.

Contact 360Dialog support.

403 - Forbidden

Meta Embedded Signup (ES) Errors

Error Message
Description
Possible Solution
Screenshot

360Dialog cannot onboard customers at this time

There is an issue with the partner's Tech Provider solution. The solution may not be live, or could be pending approval from 360Dialog.

The partner can use Integrated Onboarding instead of Embedded Signup. Contact 360Dialog support.

The business account didn't comply with our Advertising Policies or other standards

The account has been banned.

The ban must be lifted by Meta before registration. Contact 360Dialog support.

You can only create a limited number of WhatsApp Business accounts before your business verification and WhatsApp account checks are complete

Meta business portfolio has reached its WABA limit.

Unverified portfolios have a 2 WABA limit. Verified portfolios' WABA limit is 20. Business verification must be completed.

GraphQL server responded with error 3441003: Please retry in some time or reach support to get issue fixed

The user may not have sufficient permissions to onboard phone number

Double-check if the user has admin access to the Meta business portfolio. Create new user account with admin permissions, or give the existing user account admin permissions. Contact 360Dialog if the issue persists.

This number is registered to an existing WhatsApp account. To use this number, disconnect it from the existing account.

The phone number is currently registered to a WhatsApp account, and it is not possible to migrate the phone number

If the phone number is on the WhatsApp personal app, delete the WhatsApp personal app accountarrow-up-right. If the phone number is on the WhatsApp Business app, register it through Coexistence Onboarding.

Error occurred while creating WhatsApp Business account. Please try again or reach out to support for help if issue persists.

The Meta business portfolio may be restricted from placing ads

Check the portfolio's Business Support Home page on the Meta Business Manager website for any outstanding account issues.

This phone number is already registered to a WhatsApp account. To continue, migrate this phone number or disconnect it from the existing account.

Coexistence Onboarding (onboarding a WhatsApp Business app phone number to WhatsApp Cloud API) cannot continue due to one of the following:

  1. Incorrect options were selected during Embedded Signup, or

  2. The phone number is connected to another WABA and with another BSP

Make sure to follow the Coexistence Onboarding guide and attempt onboarding again.

If the phone number is connected to another WABA with another BSP, disconnect the WhatsApp Business app from WhatsApp Cloud API:

  1. Open the app,

  2. Navigate to Settings > Account > Business Platform,

  3. Press Disconnect Account.

If the steps above didn't work, or the phone number isn't on the WhatsApp Business app, contact 360Dialog support.

Your phone numebr doesn't meet the requirements to connect to the WhatsApp Business platform. More activity in the WhatsApp Business app is needed to help determine eligibility.

WhatsApp Business app account did not meet requirements for WhatsApp Coexistence.

Continue initiating conversations with customers on the WhatsApp Business app to build account activity. Reattempt onboarding in 7 days.

The business is already sharing this WhatsApp Business account with a partner. Switching partners is not supported in this flow. Disconnect the current partner in the WhatsApp Business app, then return here to connect a new partner.

The WhatsApp Coexistence-enabled phone number cannot be migrated because it is registered to another WABA with another BSP.

Contact the previous BSP's support team to remove their credit line from the WABA.

After the credit line is removed, disconnect the WhatsApp Business app from WhatsApp Cloud API:

1. Open the app, 2. Navigate to Settings > Account > Business Platform, 3. Press Disconnect Account.

Attempt onboarding again afterwards. If the previous BSP cannot remove their credit line, a full WhatsApp Business app account deletion is required. Contact 360Dialog support for assistance.

Last updated

Was this helpful?