Provide one BODY and optionally one of each other component, in HEADER, BODY, FOOTER, BUTTONS order.
- BODY: 1–1024 characters. Keep literal text before and after variables. Use sequential
{{1}}, {{2}} with example.body_text (rows of example strings), or lowercase named variables with parameterFormat: NAMED and example.body_text_named_params (objects with param_name and example). Every variable needs a non-empty sample.
- HEADER: TEXT (up to 60 characters, no formatting, line breaks or emoji) or IMAGE, VIDEO, DOCUMENT with one uploaded sample handle in
example.header_handle. A text header can have one variable. Use example.header_text for positional {{1}} or example.header_text_named_params for a named variable.
- FOOTER: Up to 60 characters of static text, without variables, line breaks or emoji.
- BUTTONS: 1–10 buttons with labels up to 25 characters. Keep QUICK_REPLY and call-to-action buttons in contiguous groups. At most two URL buttons, one PHONE_NUMBER button and one FLOW button. URLs must use HTTPS. A dynamic URL can end in
{{1}} and must provide example.url_suffix_example. The resolved example must be a valid HTTPS URL without placeholders or credentials. Phone numbers must use E.164. FLOW requires flow_id and supports navigate or data_exchange.
For media headers, upload a sample via POST /v1/templates/header-example and set example.header_handle to [data.handle] from the response. A send-time media ID from POST /v1/media, a URL, or an upload session ID is invalid here. If Meta rejects a stale sample, upload a fresh sample and replace the pending draft.
Text components reject tabs, five or more consecutive spaces and three or more consecutive line breaks.