WhatsApp error 132001 (template name does not exist in the translation): how to fix it

WhatsApp error 132001 means WhatsApp could not find an approved template that matches the name and language you sent. Meta's error reference puts it exactly: "The template does not exist in the specified language or the template has not been approved." Its fix: "Make sure your template has been approved and the template name and language locale are correct." The error is about the pair of name and language, which is why it often appears when the template looks perfectly fine in WhatsApp Manager.

Why the language code matters so much

Meta's template documentation explains that names are not unique: you can create several templates with the same name in different languages, and each one is a separate template that counts toward your limit. When you send, WhatsApp looks up the name and the language code you pass in template.language.code.

Meta's supported languages list includes separate codes for English (en), English UK (en_GB) and English US (en_US), and Hindi is hi. So a template approved as order_update in en_US cannot be sent with "code": "en", and the reverse is also true. This one mismatch causes more 132001 failures than anything else, especially when templates were created in WhatsApp Manager (which may default to a regional English) and the sending code was written with a plain en.

All the common causes

Two neighbouring codes are easy to mix up with 132001. A template paused for low quality returns 132015, and one permanently disabled after repeated pauses returns 132016. Those are quality problems with an existing template, not lookup failures. And if the template is found but you pass the wrong number of variables, you get 132000 instead.

What the error looks like

The send is usually rejected straight away (values illustrative):

{
  "error": {
    "message": "(#132001) Template name does not exist in the translation",
    "type": "OAuthException",
    "code": 132001,
    "error_data": {
      "messaging_product": "whatsapp",
      "details": "template name (diwali_offer_2026) does not exist in en"
    },
    "fbtrace_id": "AQx7Lm2pTn5VbE8rWc1sZuK"
  }
}

Read the details string carefully: it normally names the template and the language WhatsApp looked for. If it says en and your template is approved in en_US, you have found the problem without any further digging.

Step-by-step fix

1. Copy the name and language from the request that failed. Log the exact JSON your code sent, not what you think it sent.
2. Look the template up in the right account. Call the message_templates edge of the WhatsApp Business account that owns the sending number, filtered by name (example below).
3. Compare the language. If the template exists only in other languages, change your request to one of them or create a translation in the language you need.
4. Check the status. Only APPROVED can be sent. Anything else (pending, rejected, paused, disabled, appeal) cannot.
5. Check the account. If the template is missing from this account's list but you can see it in WhatsApp Manager, you are probably looking at a different WhatsApp Business account in the same business portfolio.
6. Resend with the corrected name and language code.

The lookup call:

curl -G 'https://graph.facebook.com/v24.0/<WABA_ID>/message_templates' \
  -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  --data-urlencode 'name=diwali_offer_2026' \
  --data-urlencode 'fields=name,language,status,category'

A response that explains a 132001 at a glance (illustrative):

{
  "data": [
    { "name": "diwali_offer_2026", "language": "en_US", "status": "APPROVED", "category": "MARKETING", "id": "1259544702043867" },
    { "name": "diwali_offer_2026", "language": "hi", "status": "PENDING", "category": "MARKETING", "id": "1259544702043868" }
  ]
}

Here, sending in en fails because no en version exists, and sending in hi fails until the Hindi translation is approved. Only en_US works today. Use the Graph API version your integration already uses in the URL; the name filter narrows the list to that template's versions.

A worked example

Rangoli Home creates a Diwali offer template, diwali_offer_2026, in WhatsApp Manager, in English (US), and adds a Hindi version the next day for customers in Jaipur and Jodhpur. Arjun, the developer, schedules the campaign from the brand's own system with "language": { "code": "en" } for English and "hi" for Hindi.

Every English send fails with 132001, and the Hindi sends fail too. The lookup above shows why: the English template is en_US, and the Hindi one is still PENDING. Arjun changes the English code to en_US, holds the Hindi segment until the translation is approved, and adds a check that runs the lookup before every campaign so that a language or status mismatch stops the campaign before the first send rather than after thousands of failures.

Preventing 132001

• Never hard-code the language. Store the template name and its approved language together, from the API, and send exactly that pair.
• Sync statuses. Subscribe to the message_template_status_update webhook, which Meta uses to announce status changes, and block sends of templates that are not approved.
• Do not edit templates in the middle of a campaign. An edit sends the template back to review, and sends fail until it is approved again.
• Keep one WhatsApp Business account per brand, or record which account each template belongs to, so that numbers never try to send another account's templates.
• Name templates clearly with a version or date suffix (order_update_v2), and create a new template rather than reusing a deleted name.

How Broadchat avoids 132001

In Broadchat, templates are created and listed under CRM → WhatsApp Templates and per number in the channel's Template Manager. Sync Templates pulls the current list from Meta, and status and category changes arrive through Meta's webhook, so the panel shows Approved, Pending or Rejected as Meta sees them. Campaigns, the Inbox and chatbot steps let you pick only templates that belong to the channel's own WhatsApp Business account, and the language is taken from the synced template, which removes the two most common causes. You will still see 132001 if a template is deleted or sent back to review between scheduling and sending, or if your own code calls the channel API with a name or language typed by hand.

To learn how templates are structured, read the guide to WhatsApp message templates, and if they are being rejected at review, why WhatsApp templates get rejected. The full list of codes is in the WhatsApp API error codes cheat-sheet.