How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ManyChat Page API

Page-level configuration for a connected ManyChat page: connected page info, tags, typed custom user field definitions, global bot fields, automations (flows) and folders, growth tools and One-Time Notification topics. 16 operations. Reads are limited to 100 queries per second and writes to 10; getFlows is the exception at 10 q/s. removeTag and removeTagByName delete the tag from the page and every subscriber carrying it and cannot be undone.

ManyChat Page API is one of 5 APIs that ManyChat publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Page, Tags, Custom Fields, Bot Fields, and Flows. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 16 operations across 16 paths, and defines 11 schemas. It is described by OpenAPI 3.0.0, at version beta.

Requests are made against a single base URL, https://api.manychat.com.

16 operations 16 paths 11 schemas 8 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
beta
Base URL
https://api.manychat.com
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

ManyChat Page API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Bearer). By default, every request must be authenticated.

  • Bearer — API key generated per page in the ManyChat dashboard under Settings API. Sent as Authorization: Bearer : .

Paths & Operations 16

Across 16 paths, the API surfaces 16 operations — 8 GET, 8 POST. Each is listed below with its method, path, parameters, and response codes.

Page 16

Page-level configuration: connected page info, tags, custom fields, bot fields, flows and growth tools

GET
/fb/page/getInfo
Get info
getPageInfo → 200
POST
/fb/page/createTag
Create tag
createTag body → 200400
GET
/fb/page/getTags
Get tags
getTags → 200
POST
/fb/page/removeTag
Remove tag
removeTag body → 200400
POST
/fb/page/removeTagByName
Remove tag by name
removeTagByName body → 200400
GET
/fb/page/getWidgetsdeprecated
Get widgets
getWidgets → 200
POST
/fb/page/createCustomField
Create custom field
createCustomField body → 200400
GET
/fb/page/getGrowthTools
Get growth tools
getGrowthTools → 200
GET
/fb/page/getFlows
Get flows
getFlows → 200
GET
/fb/page/getCustomFields
Get custom fields
getCustomFields → 200
GET
/fb/page/getOtnTopics
Get otn topics
getOtnTopics → 200
GET
/fb/page/getBotFields
Get bot fields
getBotFields → 200
POST
/fb/page/createBotField
Create bot field
createBotField body → 200400
POST
/fb/page/setBotField
Set bot field
setBotField body → 200400
POST
/fb/page/setBotFieldByName
Set bot field by name
setBotFieldByName body → 200400
POST
/fb/page/setBotFields
Set bot fields
setBotFields body → 200400

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Page (9 properties), BotField (5 properties), CustomField (4 properties), Folder (3 properties). Each schema is shown below with its type and property counts.

BotField
object
5 properties 5 required
CustomField
object
4 properties 4 required
Flow
object
3 properties 3 required
Folder
object
3 properties 3 required
GrowthTool
object
3 properties 3 required
OtnTopic
object
3 properties 3 required
Page
object
9 properties 9 required
ResponseError
object
3 properties 3 required
ResponseErrorMessage
object
1 property 1 required
ResponseSuccess
object
1 property 1 required
Tag
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

manychat-page-api-openapi.yml Raw ↑

Other APIs ManyChat publishes across the network.

ManyChat REST API
ManyChat Profile API
ManyChat Sending API
ManyChat Subscriber API
Where this information came from

This is an independent, third-party profile of ManyChat Page API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.