Channels · WhatsApp · Messages

Messages Overview

Base URL & auth

Prefix: /api/business/public on https://api.engagive.io (full base: https://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.

All message endpoints require WhatsApp Chats — Add permission. They are scoped to :accountId (must belong to your business).

Each send upserts a contact from to (digits with country code, no +), saves the message in Engagive chat history, then calls Meta. Response data includes Engagive `id`, `whatsapp_message_id`, `contact_id`, `contact_created`, `status`, plus `template_id` / `lang_code` when applicable (null for non-template sends).

Each linked page uses Try it → Example body to load the same variants as the Engagive Public API Postman folder (text, image, video, audio, document, location, contacts, sticker, all interactive types, reply, template, reaction).

Message endpoints

Each linked page documents one route with JSON examples (loaded from the docs repo) and a Try it panel.

Send single — text, media, interactive Interactive — presets & validation notes Send template Send reaction Reply in thread (parent wamid)

Example: full URL shape

https://api.engagive.io/api/business/public/channels/whatsapp/accounts/{accountId}/messages/send-single