Engagive API documentation

Channels · WhatsApp · Messages

Reply Messages

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.

There is no separate reply endpoint. Use POST …/messages/send-single with parent_whatsapp_message_id set to the wamid you are replying to.

POST

Send single message

Required permission: WhatsApp Chats — Add

One endpoint for text, media, interactive, location, contacts, sticker, and replies (`parent_whatsapp_message_id`). Phone to: digits with country code (no +). Examples match the Engagive Public API Postman collection.

Path
/api/business/public/channels/whatsapp/accounts/:accountId/messages/send-single
Example request body (JSON)
{
  "to": "923001234567",
  "message_type": "text",
  "content": "Hello! This is a plain text message.",
  "preview_url": false
}
Example success response (JSON)
{
  "success": true,
  "message": "Message sent successfully",
  "data": {
    "to": "923001234567",
    "message_type": "text"
  },
  "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-single