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 Subscriber API

Look up, search, create, update, tag and set custom field values on subscribers. 15 operations. A subscriber carries per-channel identity fields for Messenger, Instagram, WhatsApp, email and SMS on one record. Search operations are hard-capped at 100 results with no pagination or cursor, so a full result set is unreachable through the API when the cap is hit.

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

Tagged areas include Subscriber, Contacts, and Segmentation. The published artifact set on APIs.io includes an OpenAPI specification.

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

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

15 operations 15 paths 8 schemas 5 GET10 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 Subscriber 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 15

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

Subscriber 15

Look up, create, update, tag and set custom fields on subscribers

GET
/fb/subscriber/getInfo
Get info
getSubscriberInfo 1 param → 200
GET
/fb/subscriber/findByName
Find by name
findSubscriberByName 1 param → 200
GET
/fb/subscriber/getInfoByUserRef
Get info by user ref
getSubscriberByUserRef 1 param → 200400
GET
/fb/subscriber/findByCustomField
Find by custom field
findByCustomField 2 params → 200400
GET
/fb/subscriber/findBySystemField
Find by system field
findBySystemField 2 params → 200
POST
/fb/subscriber/addTag
Add tag to subscriber
addTag body → 200400
POST
/fb/subscriber/addTagByName
Add tag to subscriber
addTagByName body → 200400
POST
/fb/subscriber/removeTag
Remove tag from subscriber
removeSubscriberTag body → 200400
POST
/fb/subscriber/removeTagByName
Remove tag from subscriber
removeSubscriberTagByName body → 200400
POST
/fb/subscriber/setCustomField
Set custom field
setCustomField body → 200400
POST
/fb/subscriber/setCustomFields
Set custom fields
setCustomFields body → 200400
POST
/fb/subscriber/setCustomFieldByName
Set custom field by name
setCustomFieldByName body → 200400
POST
/fb/subscriber/verifyBySignedRequest
Verify by signed request
verifyBySignedRequest body → 200
POST
/fb/subscriber/createSubscriber
Create a Unified subscriber
createSubscriber body → 200400
POST
/fb/subscriber/updateSubscriber
Update subscriber
updateSubscriber body → 200400

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Subscriber (29 properties), SubscriberCustomField (5 properties), ResponseErrorWithCode (3 properties), ResponseError (3 properties). Each schema is shown below with its type and property counts.

ResponseError
object
3 properties 3 required
ResponseErrorMessage
object
1 property 1 required
ResponseErrorWithCode
object
3 properties 3 required
ResponseSuccess
object
1 property 1 required
Subscriber
object
29 properties 29 required
SubscriberCustomField
object
5 properties 5 required
SubscriberRefField
object
2 properties 2 required
Tag
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

manychat-subscriber-api-openapi.yml Raw ↑

Other APIs ManyChat publishes across the network.

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

This is an independent, third-party profile of ManyChat Subscriber 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.