WhatsApp Template Variables: {{1}} vs Named Parameters

{
  "type": "BODY",
  "text": "Hi {{1}}! Your order {{2}} ships on {{3}}.",
  "example": { "body_text": [["Layla", "OM-4821", "12 November"]] }
}

{
  "type": "BODY",
  "text": "Hi {{first_name}}! Your order {{order_number}} ships on {{ship_date}}.",
  "example": {
    "body_text_named_params": [
      { "param_name": "first_name", "example": "Layla" },
      { "param_name": "order_number", "example": "OM-4821" },
      { "param_name": "ship_date", "example": "12 November" }
    ]
  }
}

How do I send the parameters in the API call?

You send the template name, the language and a components array with the values. This is the shape for a positional template:

{
  "messaging_product": "whatsapp",
  "to": "971500000000",
  "type": "template",
  "template": {
    "name": "order_shipped",
    "language": { "code": "en" },
    "components": [
      { "type": "body", "parameters": [
        { "type": "text", "text": "Layla" },
        { "type": "text", "text": "OM-4821" },
        { "type": "text", "text": "12 November" }
      ] }
    ]
  }
}

For a named template, each entry also carries parameter_name, which must match the placeholder:

{ "type": "text", "parameter_name": "order_number", "text": "OM-4821" }

How do header media parameters work?

A media header has no text variable. At creation, the header holds an example asset handle from Meta's upload flow, and the example is reviewed with the template. At send time you pass the asset, for example an image by media ID:

{ "type": "header", "parameters": [ { "type": "image", "image": { "id": "1558081531584829" } } ] }

The ID above is the example from Meta's documentation, not a real asset.

How does this look through the OmniChannels.ai API?

Our sendbulk endpoint takes the template as form fields, per the WhatsApp API docs:

Worked example: an order-shipped template

"Souq Rafiq" (synthetic), a UAE retailer, wants a shipping update with a product image and a tracking button.

1. Write the template so that it neither starts nor ends with a variable: "Hi {{1}}, your order {{2}} has shipped and should arrive on {{3}}. Tap the button to follow it."
2. Add the header as an image, the footer as plain text, and a URL button https://shop.example/track/{{1}} with a sample such as OM-4821.
3. Submit with realistic samples for every variable, then wait for the approval status.
4. Send with the three body values, the tracking suffix and, if you override it, the header image.

curl -X POST https://api.broadnet.me/whatsapp/message/sendbulk \
  -H "Authorization: Bearer $BROADNET_TOKEN" \
  -F batchId=0 \
  -F campaignName=order-shipped \
  -F destinationNo=971500000000 \
  -F messageType=TEMPLATE \
  -F templateName=order_shipped \
  -F templateLanguage=en \
  -F bodyTemplateVariables=Layla \
  -F buttonsTemplateVariable=OM-4821

This snippet shows the field names for a single value. For several body variables per recipient, use a personalised upload instead of repeating the command. Confirm the encoding with our team for your first campaign.

How do I personalise a template from a CSV?

Use one row per recipient and one column per variable, then upload it in a personalised send.

1. Put the recipient's number in international format in the first column. See E.164 phone number format.
2. Add one column per variable, and confirm the column layout with our team for your first campaign.
3. Clean the data first: trim spaces, fix capitalisation, use one date format, and remove empty values, because an empty variable produces a broken message or a failed send.
4. Preview several rows and send to your own number first.

Data-cleaning steps are covered in send bulk SMS from Excel or CSV; they apply equally to WhatsApp.

How do I choose between positional and named?

Pick by how many people will touch the template and how many variables it has.

1. One or two variables, one owner: positional is fine and is the default.
2. Three or more variables, or several teams editing templates: use named, so each placeholder explains itself.
3. Same wording in several languages: keep the same names or numbers across versions, so one send routine can fill every language.
4. Always keep a record of which source column feeds which variable, so a later edit to the template does not shift the data.

Before you submit, read the finished message aloud with the sample values. If it sounds unnatural, reviewers and customers will think so too.

What are the common mistakes?

• Starting or ending with a variable, which Meta lists as a rejection reason.
• Skipping numbers or reusing the same number out of order in a positional template.
• Placeholder samples such as "test" that tell reviewers nothing.
• Special characters like #, $ or % inside variables.
• Wrong order at send time in a positional template, which puts the right data in the wrong place.
• Mismatched parameter_name in a named template.
• Using a variable to hide the real purpose of the message. A template whose category does not match its content can be rejected or recategorised; see the categories guide.
• Limits: this guide reports what Meta's documentation states at the time of writing. Review decisions stay with Meta and rules change, so check the linked pages.

How OmniChannels.ai helps

BroadNet is an official Meta Business Solution Provider. In OmniChannels.ai you can create WhatsApp templates with variables, media and buttons, preview them and track approval status, then send them with personalised values from the API or from an Excel or CSV upload in a campaign. Duplicate filtering and delivery reports are included. See the WhatsApp Business API page and the campaigns platform.