Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 132012: Template parameter format mismatch

Error 132012 means the number of variables may be right, but at least one is in the wrong format for its place in the template, such as text where the header expects an image.

132012
Code
Template parameter format mismatch
Meta's name
Template send
Type
On the API response
Where you see it
After fixing the cause
Retry

Quick answer

A template variable doesn't match the format the template defines. Match each value to its slot: media headers need media, button variables need the URL suffix, and named variables need the right names.

What WhatsApp error 132012 means

Meta documents 132012 as: variable parameter values formatted incorrectly, meaning the values in the request don't use the format specified in the template. It differs from 132000, where the count of values is wrong.

Why error 132012 happens

Template errors come from a mismatch between the request and the approved template, or from the template's state. The common ones:

  • Sending a text value for a header that was approved as an image, video or document header.
  • Passing the full URL for a dynamic URL button when the template only expects the variable suffix.
  • Named parameters sent with names that don't match the template, or positional values sent to a template that uses names.
  • A value of the wrong type, such as a currency or date object where the template expects plain text.

How to fix error 132012

Work through these in order; the first one that turns up a problem is usually the fix.

  • Open the approved template and list each variable slot with its component and type: header, body or button, and text or media.
  • Build the send from that list so every value lands in the matching component.
  • For dynamic URL buttons, send only the part that replaces the variable, not the base URL.
  • If the template uses named parameters, send the parameter names exactly as defined.

Should you retry after 132012?

Correct the parameter formats, then resend. The same payload will keep failing.

How error 132012 shows up in InfiQ

When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 132012, the "(#132012)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. Keep the trace IDs with the failed message: they are what support needs to look it up.

Send it through InfiQ

Frequently asked questions

What is the difference between error 132000 and 132012?+
132000 means the number of values doesn't match the number of variables in the template. 132012 means the count may be fine but a value is in the wrong format for its slot.
Why does my media header template fail with 132012?+
The header was approved as media, so it needs an image, video or document object at send time. Sending text, or leaving the header out, doesn't match the template's format.

Manage templates and sends in one place

Create, track and send approved templates from InfiQ, and see template errors next to the message that hit them.