See what each template variable is for
Templates from the API now come with each variable explained — the wording around it, an example value, and exactly where it goes — so a form built on your templates can label a field properly instead of calling it "Body 2".
Ask the API for your templates and every variable now arrives explained: the sentence it sits in, an example value, and where it belongs in a send.
What's new
- Every variable comes with its own wording — each template now lists its variables with the text either side of them, so a slot reads as "…has been paused. Date Time: {{2}}, and it will resume…" rather than "Body 2". Where a value goes was never the hard part; what it means was.
- Meta's own example value comes too — if a template was submitted with a sample for a variable, that sample now comes back with it, so a form can show a realistic value instead of an empty box.
- Everything a send can carry is listed — headers of every kind, message variables, buttons that take a value, each card of a carousel, and a limited-time offer's expiry. Buttons that need nothing from you — a call button, a fixed link — are left out rather than asked for.
- Each variable says where it belongs — so whatever your integration collects can go straight back into a send without working out the shape of the template first.
- Nothing to change — the template details you already read are untouched, and so is sending. This is added alongside them, so existing integrations carry on exactly as they are.
- The same wording in the console — the hint under each variable when you send a template by hand now comes from the same place, so a variable reads the same whether you see it in WA.cr or through your own integration.