Send WhatsApp templates with named parameters and dynamic bindings

Sending most WhatsApp templates no longer requires building the components array by hand. POST /v1/whatsapp/messages now accepts a template.parameters object keyed by each variable's name (or position, for a numbered placeholder), plus fixed keys for a media header, a location header, a button URL suffix, or an authentication code. The template version's variables array lists the keys the template takes and which are required, so you can build the object from the API response instead of guessing.

A template language can also define parameter bindings: Liquid that computes a value from the parameters you send, set with PUT a template language. A binding can read a recipient's contact record, which isn't possible for a single send, so a language with contact-reading bindings returns 422 on create-whatsapp-message and instead resolves per recipient in a broadcast. A template with parameter bindings, or with named variables in a carousel card or a button URL, accepts only parameters; sending it with components is rejected. See Components and parameters for the full key reference.

Also in this release:

• 10DLC brand registration now fills in your support email automatically. The support email on a brand is the address you sign in with, and it can't be edited; free providers like Gmail aren't accepted, so sign in with an address on your business domain before registering. See 10DLC registration.