No parameter with header-text and body Estimated reading: 2 minutes 66 views The Template Creation API allows users to create marketing templates that can be used for various communication purposes. Each template consists of a name, language, category, and content components, such as the header and body text.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 HeadersContent-Type: Should be set to application/json.Authorization: Bearer token for authentication.Request Body Parametersname (string, required): Unique identifier for the template. language (string, required): Language code in ISO 639-1 format (e.g., en_US). category (string, required): Template category, such as MARKETING. allow_category_change (boolean, required): Determines if the category can be changed after creation. components (array, required): List of template components.ComponentsEach component in the components array should have the following properties:type (string, required): Type of component (e.g., HEADER, BODY). format (string, required for HEADER type): Specifies the format of the header (e.g., TEXT). text (string, required): The actual content of the template component. Request Body{ "name": "markting_f", "language": "en_US", "category": "MARKETING", "allow_category_change": true, "components": [ { "type": "HEADER", "format": "TEXT", "text": "Our summer sale is on!" }, { "type": "BODY", "text": "Shop now and use code CR7000 to get more offer" } ] }Success ResponseStatus Code: 201 APPROVED{ "id": "333137", "status": "APPROVED", "category": "MARKETING" }NotesEnsure that the name is unique across all templates. The language field must follow ISO 639-1 format (e.g., en_US). The API requires an authorization token for security. If allow_category_change is set to false, the category cannot be modified later. The HEADER component requires a format field (e.g., TEXT).