Engagive API documentation

Channels · WhatsApp · Messages

Messages Overview

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.

All message endpoints require WhatsApp Chats — Add permission. They are scoped to :accountId.

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, interactiveInteractive — presets & validation notesSend templateSend reactionReply in thread (parent wamid)
Example: full URL shape
https://stage.api.engagive.io/api/business/public/channels/whatsapp/accounts/{accountId}/messages/send-single