WhatsApp error 132001: Template does not exist

Code 132001 means the platform could not find an approved template matching the name and language you supplied on this WhatsApp Business Account. Two different problems share it: the template genuinely does not exist under that name or language, or it exists but is not in APPROVED status (it may be pending, rejected, paused in a way that removes it, or deleted). Either way the send is refused with HTTP 404.

Language is the usual culprit. A template is approved per language, and the language code in your request must match exactly: en_US and en are different entries, as are pt_BR and pt_PT. Template names are case-sensitive and use lowercase letters, numbers, and underscores. Sending a template that was approved on a different WABA (for example, a staging account) also produces 132001 because templates are scoped to the WABA.

Nothing about the recipient, window, or parameters is being evaluated yet; lookup failed first.

132001 is synchronous - the lookup fails before anything is queued, so there is no webhook follow-up. The classic production incident: a template is deleted or renamed in WhatsApp Manager by a marketing teammate, and every automated flow referencing it starts failing at once; nothing changed in code, which is why deploys get blamed first. Check the exact name-language pair you should be sending with the WhatsApp template checker, and if the underlying problem is a rejection rather than a lookup, work through the template rejection guide. BSP wrinkle: providers that manage templates on your behalf keep their own identifiers (Twilio content SIDs, for example), and a template visible in the provider dashboard may not yet be approved on the WABA - the Meta-side status is the one that decides 132001.

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

Resolve templates at runtime from a cached list of approved templates on the production WABA, keyed by name and exact language, and refuse to send a combination that is not in the cache. Subscribe to message_template_status_update so approvals, rejections, and deletions update the cache, and promote templates between environments with a script rather than by hand. Template count, naming, and length ceilings are listed under template limits.