Publish text, links, and media to a connected Page. Text-only posts are fine, and scheduling works out of the box.
Meta API · Facebook · Instagram · Threads
Three Meta surfaces.
Three Meta surfaces.
One integration.
Facebook, Instagram, and Threads each have their own rules, but they don't need three integrations in your code. MonoChalk exposes all of Meta behind the same post request and account model you use for every other network.
THE THREE SURFACES
What each Meta target does.
Media-first: every post carries an image or video. MonoChalk enforces that on validation so you catch it early. Instagram details →
Threads
Short-form text and media posts to a connected Threads profile, delivered and tracked through the same status model.
ONE REQUEST, MANY SURFACES
Post to all three at once.
List the Meta accounts you want in one call. Each surface is delivered independently, so a failure on one (say, a missing Instagram image) never blocks the others.
Read the API overviewPOST /v1/postsfacebook · instagram · threads
{
"account_ids": ["fb_01", "ig_02", "th_03"],
"text": "Meet the new release.",
"media": [{ "media_id": "med_77" }]
}QUICK ANSWERS
Meta publishing FAQ.
Which Meta platforms does MonoChalk support?
Facebook, Instagram, and Threads, all through the same unified post payload used for the other supported platforms.
Can I schedule Facebook and Instagram posts through the API?
Yes. Send a post with a scheduled_at timestamp to publish later, or omit it to publish immediately, and track the result through per-target status and signed webhooks.
How does MonoChalk handle the differences between Meta surfaces?
MonoChalk's Meta adapters apply each surface's rules — for example Instagram requiring media — and failures return normalized errors with the raw platform context so you can debug quickly. See the unified API →
READY TO BUILD?
Join the private beta