Engagive API documentation

Getting started · WhatsApp

Set up in the business portal first

Before writing code against the Engagive HTTP API, complete these steps in the Engagive business portal. That is where you issue a long-lived token and copy the exact account id and URLs for your WhatsApp account.

Meta vs Engagive ids

The Engagive WhatsApp account id in API URLs is not the same thing as Meta's WhatsApp Business ID. Always use the id shown on the HTTP API tab (and in paths as account_id). The portal also shows the Meta WABA id for reference in Meta Business Suite only.

  1. 1

    Sign in to the business portal

    Open the Engagive business application in your browser and sign in with your business user account. Production URL: https://stage.app.engagive.io. You need a user with permission to view the relevant WhatsApp account and to use the API (same roles as in the portal).
  2. 2

    Create an API access token (Profile)

    Go to Profile (gear icon on your user card in the sidebar, or /business/profile). In the API access token section:
    • Choose token validity (7 days up to 365 days).
    • Click Generate API token and confirm in the dialog.
    • Copy the token once and store it in a secret manager or your server config—treat it like a password.
    Use this value as Bearer on API requests (see Authentication).
  3. 3

    Open your WhatsApp account → HTTP API tab

    In the sidebar, open Channels, choose your WhatsApp channel, then open the account you want to integrate. Select the HTTP API tab. There you can copy:
    • Engagive WhatsApp account id — this is {account_id} in all public API paths.
    • Public API base URL and this account’s public API root — matches the docs (production: https://stage.api.engagive.io/api/business/public).
    • An example GET URL you can try with your token (e.g. template lookup categories).
    • Portal / business API path — for the web app only; public integrations use the public paths instead.
  4. 4

    Call the public API

    Combine the token, host, prefix, and account_id as described in WhatsApp API overview and Authentication. Example request line:
    Example
    GET https://stage.api.engagive.io/api/business/public/channels/whatsapp/accounts/{account_id}/templates/lookups/categories
Authorization: Bearer <your_api_access_token>

Security

Do not embed API tokens in mobile apps or public front-end code. Prefer server-to-server calls. Generating a new token does not automatically revoke older tokens until each one expires—protect every copy you create.

Next

AuthenticationBearer header and token rules.Errors & responsesStatus codes and JSON shape.WhatsApp API overviewBase URL, checklist, endpoint map.PostmanCollection and environment (when published).