WhatsApp error 132000 (template parameter count mismatch): count every variable, not just the body

WhatsApp error 132000 means the number of values in your template message does not match the number of variables in the template. Meta's error reference says: "The number of variable parameter values included in the request did not match the number of variable parameters defined in the template." Its fix is to make sure "the request includes values for all of the parameters required by the template." The good news hidden in this error is that the template name, language and approval are fine. If they were not, you would get 132001 instead.

How WhatsApp counts parameters

A template is made of components: an optional header, the body, an optional footer and optional buttons. Variables can live in the header (text headers allow one variable), in the body, and in URL buttons with a dynamic suffix. Authentication templates also carry the code in a button. In the send request each of these gets its own entry in template.components, and WhatsApp compares the count component by component.

Templates that use named parameters (created with parameter_format set to named) are matched by parameter_name instead of position, but the rule is the same: every variable needs a value.

The six common causes

1. Header or button variable forgotten. The body is perfect, but the text header's {{1}} or the tracking button's suffix has no value. This is the most frequent cause.
2. All values pushed into the body. Four values sent in the body for a template that has one header and three body variables.
3. Empty fields dropped. Code that filters out null or empty CRM fields (a missing city or order date) sends two values instead of three.
4. Template edited later. Someone added {{4}} for a delivery slot in WhatsApp Manager; the integration still sends three.
5. Different language version. The Hindi version of a template was written with one variable fewer than the English one, and the code uses the English count for both.
6. Wrong template, same name prefix. order_shipped and order_shipped_v2 differ by one variable, and the payload was built for the other one.

What the error looks like

132000 normally comes back immediately in the response to the send request, so the message is never queued. Illustrative response (the details text varies):

{
  "error": {
    "message": "(#132000) Number of parameters does not match the expected number of params",
    "type": "OAuthException",
    "code": 132000,
    "error_data": {
      "messaging_product": "whatsapp",
      "details": "body: number of localizable_params (2) does not match the expected number of params (3)"
    },
    "fbtrace_id": "Ab3Kq9XyTmL2pRw7Nc4sVuE"
  }
}

The details string often names the component (header, body or button) and both counts. Start there.

Step-by-step fix

1. Log the exact request that failed, including template.name, template.language.code and every component.
2. Fetch the template definition for that name and language from the WhatsApp Business account that owns the sending number: GET /<WABA_ID>/message_templates?name=delivery_update&fields=name,language,status,components
3. Count placeholders per component in the response: the header text, the body text, and every button whose url contains {{1}}.
4. Rebuild the components so that each part gets exactly that many values, in order, with buttons addressed by their zero-based index.
5. Replace empty values with a sensible fallback ("Customer", "your order") rather than removing them. Keep the fallback realistic, because it reaches the customer.
6. Resend one test to an internal number, then release the batch.

A worked example

Sunrise Clinic in Pune sends appointment reminders with the utility template appointment_reminder_v2: body "Hi {{1}}, your appointment with {{2}} is on {{3}}. Reply to reschedule." and a URL button https://sunriseclinic.in/a/{{1}} that opens the booking. Meera, the developer, wrote the reminder job when the template had no button. After the front desk added the button and the template was approved again, every reminder failed with 132000.

The details string said the button parameter was missing. Meera added a button component with sub_type: "url", index: "0" and the booking code SC7741 as its text, and changed the job to read the template's components each morning before sending. She also found a second bug while testing: patients without a doctor assigned had {{2}} dropped, so she now sends "our doctor" as the fallback.

Codes that are easy to confuse

Preventing 132000

• Treat a template edit as a code change: re-read the components after Meta approves the edit.
• Version names (_v2, _v3) when the variable count changes, so old code cannot send the new template by accident.
• Keep one parameter builder for all channels, so campaigns, bots and order webhooks all count the same way.
• Test every language version separately.

How Broadchat helps

When you pick a template in Campaigns, Broadchat reads the synced template and shows a field for each variable (BODY VARIABLE #1, #2…) and for each button payload, and a template with a media header cannot be launched until you upload the file or paste its URL. For CSV audiences, Map Variables links each variable to a column. If a send still fails, the reason shows as "The number of template variables does not match the template." with code 132000 in message info. Code that calls the channel API directly with hand-built parameters is checked by Meta, not by the panel, so the steps above still apply there.

Read the guide to sending template messages through the API, the broader WhatsApp message templates guide, and the full WhatsApp API error codes cheat-sheet.