No parameter with header-text and body and footer

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 body text.

Endpoint

http://{{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 key

Request Headers

• Authorization: Bearer token for authentication.
• Content-Type: Should be set to application/json.

Request Body Parameters

• name (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.

Components

Each component in the components array should have the following properties:

• type (string, required): Type of component (e.g., HEADER, BODY, FOOTER).
• 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_g",
  "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"
        },
        {
        "type": "FOOTER",
        "text": "Thank you for choosing us!"
        }
    ]
}

Success Response

Status Code: 201 APPROVED

{
    "id": "333137",
    "status": "APPROVED",
    "category": "MARKETING"
}

Notes

• Ensure 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).
• The FOOTER component is an optional text field that typically contains closing remarks.