Create or Update Localization
Use this endpoint after creating a new template to define or update its WhatsApp-facing content - the language, body, header, buttons, and other components.
Required token scopes: Manage WhatsApp templates
Note that this can’t be used for already-submitted templates. If you want to update any of these fields and your template was already submitted, create a new template instead.
After a successful request, the template is visible in Texter as a preview. When creating a template via the API for the first time, we recommend reviewing it in Texter before submitting it for approval.
הרשאות
API token generated in Texter: gear icon → Developers → API Tokens. When creating a token, assign it the scopes required by the endpoints you plan to call - each endpoint lists its required scopes.
פרמטרי נתיב
The account ID of the channel in Texter. For WhatsApp channels this is the phone number connected to the account (e.g. 972586640430)
The unique identifier of the template. This is either the custom name assigned when the template was created, or the system-generated name returned by the Create New Template endpoint (under the name field)
^[a-zA-Z0-9_-]+$גוף
The localization language code. Must be a lowercase IETF language tag supported by WhatsApp (e.g. he, en, en_US)
Array of template components. At least one is required. Each item is one of HEADER, BODY, FOOTER, BUTTONS (one of each type max). HEADER supports format values IMAGE, VIDEO, DOCUMENT (with example.header_handle) and LOCATION. BUTTONS contains 1-3 buttons: either up to 3 QUICK_REPLY buttons, or up to 2 call-to-action buttons (mix of URL, PHONE_NUMBER, FLOW) - WhatsApp does not allow mixing the two groups
1Optional defaults used when sending the template (does not affect WhatsApp approval). Useful for pre-filling header media, body variables or button payloads
תגובה
The updated template object with the localization added under localizationDrafts. Field-by-field reference: The Template object
A WhatsApp template in Texter, including internal behavior (chat routing rules, departments, defaults) and provider state (WhatsApp approval status, localized content)
Unique identifier of the template in Texter
"6891bb93481ccea320113a91"
Internal template name (also used as the template ID in API calls)
"bulk_marketing_272"
Human-readable title shown in Texter's UI
How this template is intended to be sent: inbox (1-to-1) or bulk (broadcast)
inbox, bulk Status the chat moves to after the recipient replies to this template
0, 1, 2, 3, 4 When the template was created (epoch ms)
Department IDs allowed to use this template. Can be empty
Whether this is the default template for the account. Only one template can be default
Bot node to trigger after reply, if chatStatus routes to bot
Specific bot to run after reply, if chatStatus routes to bot
Text automatically sent when the recipient replies to the template
Agent (email) the chat is assigned to after the recipient replies
Department ID the chat is assigned to after the recipient replies
File automatically sent when the recipient replies, when configured
Channel adapter that owns this template (relevant when multiple WhatsApp account types are connected)
The channel account this template belongs to
The template as registered with WhatsApp
Default send values by language code, prefilled when sending the template if the caller does not provide overrides
Map of language code to draft localization (created but not yet submitted/approved)