Home/HighLevel/Features/Reselling Products/HighLevel guide to fixing error 131000 for WhatsApp

Payments and Sales

HighLevel guide to fixing error 131000 for WhatsApp

In short

Error 131000 is a generic HTTP 500 response from the WhatsApp Cloud API indicating an unknown failure. It can stem from server outages, token problems, account restrictions, template issues, phone number format errors, or app misconfiguration. Following a systematic checklist restores message delivery.

AreaReselling Products · WhatsApp
Used forDigital marketing agency, Ecommerce retailer, Customer support center
Setup steps8 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Agency owners who resell WhatsApp messaging, need reliable delivery for client campaigns.
  • Ecommerce merchants using WhatsApp for order updates, must keep notifications flowing.
  • Customer support teams that rely on WhatsApp for after hours replies, require template compliance.

02Error 131000, explained

The error appears in API responses when the WhatsApp Cloud service cannot process a request for any reason it cannot name. The platform returns a 500 status with code 131000 and a generic message. Because the root cause is hidden, the resolution must examine several account and configuration areas.

The troubleshooting workflow lives outside any single HighLevel screen. It uses external Meta tools such as the platform status page, the Access Token Debugger, Business Suite, and the Developer Console. The steps are performed in order, starting with checking for a broad outage and ending with creating a fresh app if earlier checks do not help.

03How businesses use error 131000

  • Digital marketing agency. The agency checks the Meta status page before contacting clients about message drops. If the platform is healthy, the agency validates its permanent system user token and confirms all client templates are active, then retries the failed messages.
  • Ecommerce retailer. The retailer verifies that the order status template used for shipping updates is active and matches the language code. It also confirms each customer’s phone number follows the required international format before sending the notification.
  • Customer support center. Support staff ensures the WhatsApp Business Account remains active and not flagged. When a free form reply is needed after the 24 hour window, they switch to an approved template to avoid the 131000 error.

04The numbers and rules that matter

  • Error 131000 is returned as an HTTP 500 Internal Server Error.
  • It can be caused by sending a free form message outside the 24 hour customer service window.

05How to set up and use error 131000 in HighLevel

Resolve error 131000

  1. Visit metastatus.com/whatsapp business api to see if Meta reports an outage. If an outage is confirmed, wait for resolution and do not continue troubleshooting account specific settings.
  2. If no outage is reported, wait a few minutes and resend the message. Wait at least 30 to 60 seconds before the first retry and use exponential backoff for any further attempts.
  3. Open the Access Token Debugger, paste your token, and verify it is valid, unexpired, and includes whatsapp_business_management and whatsapp_business_messaging permissions.
  4. In Meta Business Suite, confirm the WhatsApp Business Account is active, the phone number is connected, the quality rating is not red, and no policy violations or pending actions exist.
  5. Open Message Templates in Meta Business Manager and ensure the template is active, its name matches exactly (case sensitive), and the language code matches the approved version.
  6. Check that the recipient number is formatted with the full international country code and contains no spaces, hyphens, or symbols.
  7. If the error persists, create a new app in the Meta Developer Console, add the phone numbers and templates, generate a new permanent system user token, and point the webhook to the new app.
  8. If the error still occurs, open a support ticket and include the failing payload, full error response, timestamps, frequency, affected resources, and which steps have already been completed.

06Things to know before you rely on it

  • Error 131000 is a generic server side failure and does not indicate a specific problem.
  • The error may be caused by temporary Meta outages, so waiting before troubleshooting can resolve it.
  • Creating a new Meta app is a community verified workaround for persistent cases.

07If something goes wrong

  • Error persists after completing all diagnostic steps. Open a support ticket and provide the full API request, error response, timestamps, affected recipients, and which steps have already been run.

08How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

When the error only shows up a few times and a quick retry gets the message through, fixing it avoids missed conversations and wasted effort.

If the error keeps popping up despite a healthy token and correct templates, rebuilding a new app may be a heavy lift, and you may need to involve Meta support and accept the downtime rather than keep chasing a stubborn internal glitch.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about error 131000.

Error 131000 appeared suddenly and everything was working before, what happened?

A sudden appearance usually means a temporary Meta server issue or a short lived token expiration. Check the status page first, then verify the token and account health.

Should I retry immediately when I get error 131000?

Yes. Wait 30 to 60 seconds before the first retry and use exponential backoff for subsequent attempts. If the error repeats, move on to deeper diagnostics.

Will I be charged for messages that return error 131000?

No. Messages that fail before delivery do not open a conversation and are not billed.

Error 131000 is only happening to one specific recipient, is it their issue?

If only one contact is affected, the number may be malformed, not on WhatsApp, or outside the allowed window. Test with a different valid number or send a template message to confirm.

Meta has no official fix for this error, what can I actually do?

Follow the step by step checklist, especially checking the token, WABA status, and template health. If those are correct, create a new app in the Developer Console and reconfigure the webhook and token.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.