Contents

Guide

Compatible with ManyChat's API

What matches ManyChat's public API exactly, and what is ours.

Growth Dept Engage's public API follows ManyChat's published API (its Page API and Profile API), so a tool written for ManyChat can switch by changing two things: the base address and the key.

ManyChatEngage
Base addresshttps://api.manychat.comhttps://engage.growthdept.ai/api
KeyFrom ManyChat's settingsFrom Settings, then API, in the same <page id>:<secret> shape

What matches

  • All 35 operations: the same paths, methods, parameter names and body keys.
  • The same answers: the success envelope, the object shapes (page, tag, custom field, bot field, growth tool, flow, folder, subscriber) and the two error shapes.
  • The same numbered errors (3011, 3021, 304X, 2011, 2012) and the same per-operation limits, including sendFlow's 100 calls per contact per hour.
  • The v2 dynamic content format for sendContent, external requests and dynamic buttons.

Where we decided

ManyChat's published spec leaves some things unsaid. Where it does, we chose and wrote it down:

  • 401, 404, 405, 429 and 500 answers use the same error envelope; 429 adds Retry-After.
  • Something that doesn't exist answers 400 with a message.
  • Values a contact lacks come back as null.
  • Message tags follow Meta's current rules, which no longer allow most of the older tags.

What we add

  • An OpenAPI file at /api/openapi.json, generated from the same code that serves the API.
  • Signed webhooks for contact, message, flow and conversation events.
  • Account keys also work on our own app endpoints, with a manager's permissions.

Moving your data

To bring tags, fields, growth tools, flow names and contacts across from ManyChat, use the import; see Import from ManyChat.

ManyChat is a trademark of its owner. Growth Dept Engage is not affiliated with or endorsed by ManyChat.