Engagive API documentation

Channels · WhatsApp · Messages

Send Template

Base URL & auth

  • Prefix: /api/business/public on https://stage.api.engagive.io (full base: https://stage.api.engagive.io/api/business/public).
  • Header: Authorization: Bearer <token> — create the token under Profile → API access token in the business app.
  • See also: Authentication, Errors & responses.

content_json must match your approved template structure on WhatsApp (components, parameters, language).

POST

Send template

Required permission: WhatsApp Chats — Add

content_json is passed through to Meta (`template_name` / `lang_code` / `components`, or the shape your meta-apis service expects).

Path
/api/business/public/channels/whatsapp/accounts/:accountId/messages/send-template
Example request body (JSON)
{
  "to": "923001234567",
  "content_json": {
    "template_name": "hello_world",
    "lang_code": "en_US",
    "components": [
      {
        "type": "BODY",
        "parameters": [
          {
            "type": "text",
            "text": "Hello"
          }
        ]
      }
    ]
  }
}
Example success response (JSON)
{
  "success": true,
  "message": "Template message sent successfully",
  "data": {
    "to": "923001234567",
    "message_type": "template"
  },
  "metaResponse": {}
}

Try it

Runs in your browser — token is not stored

If the request fails with a network / CORS error, your API may not allow browser calls from this site. Use curl, Postman, or your server instead. See Postman.

Full request URL
POST https://stage.api.engagive.io/api/business/public/channels/whatsapp/accounts/1/messages/send-template