No parameter head , body and footer Estimated reading: 2 minutes 64 views This document provides detailed information about the Utility Templates used for communication purposes. These templates allow businesses to send structured messages to users for transactional or informational purposes.Endpointhttp://{{your_domain}}/api/v1.0/{{phone_number_id}}/{{key}}/message_templates{{your_domain}}: Your domain URL where the API is hosted. {{phone_number_id}}: The unique identifier of the phone number used for sending messages. {{key}}: Your API key for authentication.How to create keyRequest HeadersAuthorization: Bearer token for authentication. Content-Type: Should be set to application/json.Template InformationUtility Template GName: utility_g Language: en_US (English – United States) Category: UTILITY Allow Category Change: YesComponentsUtility Template G ComponentsThe utility_g template consists of a Header, a Body, and a Footer component.Header:Type: HEADER Format: TEXT Text: Order Infermation Purpose: Provides a title for the message, indicating that it contains order-related details. Body:Type: BODY Text: Item no CR7000 is confirmed! Purpose: Serves as a confirmation notification for an item, order, or transaction. Footer:Type: FOOTER Text: Thank you for choosing us! Purpose: Provides a closing remark to thank the recipient.Example Message GenerationUtility Template GHeader: Order Infermation Body: Item no CR7000 is confirmed! Footer: Thank you for choosing us!Sample Request{ "name": "utility_g", "language": "en_US", "category": "UTILITY", "allow_category_change": true, "components": [ { "type": "HEADER", "format": "TEXT", "text": "Order Infermation" }, { "type": "BODY", "text": "Item no CR7000 is confirmed!" }, { "type": "FOOTER", "text": "Thank you for choosing us!" } ] }Success ResponseStatus Code: 201 APPROVED{ "id": "xxxxxx", "status": "APPROVED", "category": "MARKETING" }NotesThe template allows changes to the category since allow_category_change is set to true. This template is intended for utility purposes, such as order confirmations, service updates, or other transactional messages. The message format is mostly fixed and does not include dynamic placeholders, making it suitable for standard notifications.