WhatsApp error 132012: Template Parameter Format Mismatch

Code 132012 means a parameter value is present and the count is right, but the value is not in the format the template expects. Template parameters are typed: text, currency, date_time, image, video, document, location, and so on. A currency parameter must be an object with fallback_value, code, and amount_1000; a date_time parameter needs a fallback_value; a media header needs a media object with an id or link, not a string. Passing a plain string where a structured object is required, or a structured object where text is expected, produces 132012.

It also appears when a header parameter type does not match the template's header (a text parameter for an image header, or an image for a document header), and when a button component's sub_type or index does not match the approved button layout.

Approval, language, and recipient are all fine; the platform cannot map your value onto the slot's type.

Model template parameters as typed structures generated from the template definition, so a currency slot cannot receive a string at compile time. Keep one validated example payload per template in source control and run it against a test recipient whenever the template changes. Parameter object shapes per type are validated by the template checker, and the count-level version of this failure is 132000; both are covered in the error-code guide.