Resolving WhatsApp Error 131000 — Something Went Wrong
Understanding Error 131000
Error 131000, officially titled "Something Went Wrong," is a generic error returned by the WhatsApp Cloud API when a message fails to send. It appears as an HTTP 500 Internal Server Error and indicates that something has gone wrong on Meta's servers or within your account configuration, but the system cannot provide a more specific reason. Because it covers many possible underlying issues, systematic troubleshooting is required to identify the root cause.
Common Causes of Error 131000
The following are the most frequent triggers for this error:
- Temporary Meta Server Issues: Downtime, maintenance, or performance problems on Meta's WhatsApp Business Platform servers can cause this error to appear broadly.
- Invalid or Expired Access Token: The access token used for API authentication may have expired, been revoked, or lack the necessary permissions (whatsapp_business_management and whatsapp_business_messaging).
- Restricted WhatsApp Business Account (WABA): If your WABA is flagged, restricted, or under review due to policy violations or low quality ratings, messaging may fail with this generic error.
- Unapproved or Invalid Message Template: Attempting to send a template that is still in review, rejected, paused, or disabled, or using a template name or language that doesn't match the approved version.
- Sending Outside the 24-Hour Window: Trying to send a free-form (non-template) message to a contact who hasn't messaged you in over 24 hours.
- Incorrect Phone Number Format: The recipient's phone number is missing a country code, contains invalid characters, or is otherwise malformed.
- Configuration Issues: Problems with your Meta Developer app setup, such as a misconfigured webhook, incorrect phone number ID association, or stale system user token.
Step-by-Step Resolution Guide
Step 1: Check for Platform Outages
First, visit Meta's status page for the WhatsApp Business API to see if there is a confirmed, active outage or service degradation. If a platform-wide issue is reported, wait for Meta to resolve it before proceeding. No account-level troubleshooting will help during a server outage.
Step 2: Wait and Retry
If no outage is reported, wait a few minutes and attempt to send the message again. Error 131000 is often transient and may resolve on its own after a short period. If the error persists consistently, continue with the following steps.
Step 3: Verify Your Access Token
Use the Meta Access Token Debugger tool to inspect your token. Ensure it is valid, has not expired, and includes both the whatsapp_business_management and whatsapp_business_messaging permissions. The token should be a permanent system user token, not a short-lived one. If the token is expired or lacks permissions, generate a new permanent token in your Meta Developer dashboard and update it in your CRM's integration settings.
Step 4: Check Your WhatsApp Business Account Status
Log into Meta Business Suite and navigate to your WhatsApp Business Account. Verify that:
- Your WABA status shows as Active (not Restricted, Flagged, or Disabled).
- Your connected phone number's status is Connected and its quality rating is not in a red or poor state.
- There are no outstanding policy violations or account reviews pending.
Step 5: Review Message Templates and Recipient Window
Confirm that any message template you are trying to use has an Approved status in Meta Business Manager. Double-check that the template name and language code in your API request exactly match the approved template. If you are sending a free-form message, ensure the recipient has sent you a message within the last 24 hours to keep the conversation window open.
Step 6: Validate Phone Number Format
Ensure the recipient's phone number is in the correct international format: it must start with a country code and contain only digits (e.g., 14155551234). Remove any spaces, parentheses, dashes, or other special characters.
Step 7: Review App and CRM Configuration
In your Meta Developer app, check that your webhook is correctly configured and active. Verify that the Phone Number ID used in your API requests matches the ID associated with your approved phone number in the developer app. Ensure your CRM integration is using the correct, up-to-date Phone Number ID and Business Account ID.
Prevention Tips
- Regularly monitor your access token's expiration date and renew it proactively.
- Always use approved templates and verify their status before launching campaigns.
- Maintain high-quality messaging practices to avoid WABA restrictions.
- Implement robust error logging in your CRM to catch and retry transient errors automatically.
- Keep your Meta Developer app and webhook configurations up to date after any changes.