Managing Templates

Contents

• Create a Template
• Create from Library
• Check Approval Status
• Get Template Details
• Update a Template
• Delete a Template

Create a Template

The --template-definition parameter is a blob type — base64-encode the JSON.

Utility Template (transactional)

Marketing Template (with image header)

First, upload the header image using create-whatsapp-message-template-media to get a media handle (see managing-media.md). Then use the returned handle in the template:

Authentication Template (verification codes)

Authentication templates do not require parameter_format — Meta handles the OTP parameter automatically. The COPY_CODE button type lets recipients tap to copy the code.

Expected Output

Rules

• parameter_format: MUST be "positional" when using {{N}} parameters
• example: MUST include sample values for each component — Meta requires this for review
• UTILITY body MUST be clearly transactional; ambiguous text gets reclassified as MARKETING
• Template names: lowercase letters, numbers, underscores only

Choosing the Right Category

Meta enforces strict categorization rules. Choosing the wrong category causes reclassification (UTILITY → MARKETING), which changes pricing and may disrupt sending. Select the correct category upfront:

Common reclassification triggers (UTILITY → MARKETING):

• Body text contains promotional language (“Get X% off”, “Limited time”, “Shop now”, “Don’t miss”)
• Template includes a call-to-action unrelated to the transaction (e.g., “Check out our new products”)
• Greeting or introduction without referencing a specific user-initiated action
• Coupon codes or discount offers included alongside transactional content
• Generic “updates” that aren’t tied to a specific order, appointment, or account event

How to avoid reclassification:

1. Keep UTILITY templates focused on a single transaction — reference the specific order/appointment/account action
2. Do NOT mix promotional content into transactional templates — create a separate MARKETING template for promotions
3. Use explicit transaction references in the body: “Your order #{{1}}”, “Your appointment on {{1}}”, “Your payment of {{1}}”
4. If in doubt, use MARKETING — it always works; reclassification only happens UTILITY → MARKETING, never the reverse
5. Configure event destinations to receive TEMPLATE_STATUS_UPDATE events that alert you to reclassifications in real-time

Detecting reclassification after the fact:

• Via event destinations: "eventType": "TEMPLATE_STATUS_UPDATE" with previousCategory and newCategory
• Via API: list-whatsapp-message-templates — compare templateCategory against your expected category
• Recovery: Delete the reclassified template and recreate with corrected content or as MARKETING

Create from Library

Browse and use pre-approved Meta library templates:

Check Approval Status

Response fields are templateStatus and templateCategory (NOT status/category):

• UTILITY: minutes to 24h. MARKETING: hours to 24h.
• MUST NOT send with PENDING or REJECTED status.

Get Template Details

Use this to retrieve component structure before sending an existing template.

Update a Template

The --template-components parameter is a blob type — base64-encode the JSON components array. Updated templates go back to PENDING for Meta re-review.

Delete a Template

⚠️ The delete parameter is --template-name (NOT --meta-template-name, NOT --meta-template-id). There is no --meta-template-name parameter — it does not exist.

Always include --delete-all-languages to avoid InvalidParametersException.