WhatsApp error 132000: template param count mismatch

WhatsApp error 132000 means the number of values you sent for the template's variables does not match the number of variables the template contains. Meta refuses the message without sending it. Count the variables of the approved template, header and body, then send exactly one value per variable, in the right order.

What does error 132000 mean?

"The number of variable parameter values included in the request did not match the number of variable parameters defined in the template." — Meta, Cloud API error codes

Meta asks you to make sure the request includes a value for every parameter the template requires. The title that comes with the code in the message field is "Template Param Count Mismatch" (360dialog's list).

A template declares its variables in a format chosen at creation (Meta, Templates, parameter formats):

When does error 132000 happen?

• A forgotten header variable: the title "Order {{1}} shipped" has its own variable, which is not filled by the body's.
• A template edited after the integration: a variable was added to the text, the code still sends the old number of values.
• A campaign with uneven variables: some recipients have two values, others one.
• An empty or missing array because a piece of data was missing in your app (unknown first name, an order number filtered out as null).

Where do you see it in Genuka WA?

Genuka WA classifies every 132xxx code as template: the error is in the request, and sending it again unchanged will always fail.

How do I fix error 132000?

# 1. The template as approved
curl https://wa.genuka.com/api/v1/templates/tpl_123 \
  -H "Authorization: Bearer $GENUKA_WA_API_KEY"
# "components": [
#   { "type": "HEADER", "format": "TEXT", "text": "Order {{1}} shipped" },
#   { "type": "BODY", "text": "Hi {{1}}, your parcel arrives {{2}}." }
# ]

# 2. One value for the header, two for the body
curl -X POST https://wa.genuka.com/api/v1/messages \
  -H "Authorization: Bearer $GENUKA_WA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "connectionId": "con_1",
    "to": "+237690000001",
    "template": {
      "name": "parcel_shipped",
      "language": "en",
      "header": { "text": "ORD-1042" },
      "body": ["Awa", "tomorrow"]
    }
  }'

How do I prevent error 132000?

• Validate before sending, with a counter like the one above, and refuse an incomplete request locally: the error shows up earlier and names the missing data.
• Version your templates (parcel_shipped_v2) when you change their variables, rather than editing a template your code already relies on.
• Check every campaign recipient before POST /api/v1/campaigns: the same number of values for everyone, no empty value.
• Check the format too: a template created with named parameters is filled with bodyNamed, not with an array.

Related error codes

• 132001: the template itself cannot be found in that language, or is not approved.
• 132015: the template is paused for low quality.
• 131047: the 24-hour window is closed, hence the switch to a template.

FAQ

Do the examples given at creation count at send time?

No. Examples are there for Meta's review of the template; at send time you provide the real values, one per variable.

Does the order of values matter?

For a positional template, yes: the first value fills {{1}}, the second {{2}}. For a named template, no: Meta accepts values in any order.

Why does my whole campaign fail with 132000?

Because the error comes from the shape of the variables, which is the same for every recipient. Genuka WA does not retry a template error, and a campaign that was already launched only resends its recipients that are still pending: fix the variables, then create a new campaign.

Sources

• Meta — Error codes
• Meta — Templates overview, parameter formats
• 360dialog — API error message list