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

Send Dynamic Block content and trigger automations for a subscriber across Messenger, Instagram and WhatsApp. 3 operations. This is the surface governed by Meta policy rather than by ManyChat: outside the 24-hour messaging window a message tag is required (error 3011), One-Time Notification sends need a token for the topic (3021), and channel restrictions surface as the 304X error family. sendFlow is additionally capped at 100 queries per given subscriber per hour. There is no idempotency key, so a retry delivers a duplicate message.

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

Tagged areas include Sending, Messaging, and Broadcast. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version beta.

Requests are made against the base URL https://api.manychat.com.

3 operations 3 paths 4 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

ManyChat Sending API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Bearer).

Paths & Operations 3

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

Sending 3
POST
/fb/sending/sendContent
Send content to subscriber
b6ae94031676b69a57eb2ad5ea1413f9 body → 200400
POST
/fb/sending/sendContentByUserRef
Send content to user ref
637120a69445b2892f725cbfeaf347ca body → 200400
POST
/fb/sending/sendFlow
Send Automation to subscriber
28f1abbb07b0d4773b846dbeb3880e3c body → 200400

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Response_Error_With_Code (3 properties), Response_Error (3 properties), Response_Success (1 property), Response_Error_Message (1 property). Each schema is shown below with its type and property counts.

Response_Error_Message
object
1 property 1 required
Response_Error
object
3 properties 3 required
Response_Error_With_Code
object
3 properties 3 required
Response_Success
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

manychat-sending-api-openapi.yml Raw ↑

Other APIs ManyChat publishes across the network.

ManyChat Page API
ManyChat Subscriber API
ManyChat Template API
Where this information came from

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