How to schedule Threads posts (and what the API really allows)

Threads is the youngest network with a real public API, and the content around it shows: half the guides predate the API, and the other half guess. We publish to Threads in production — our app went through Meta’s review for it — so this is the actual state of scheduling Threads posts: what the API permits, the numbers that shape it, and the one architectural fact that explains how every Threads scheduler works.

Can you schedule Threads posts?

Yes. Threads has an official public API that supports publishing text posts, images, carousels and video, plus replies and insights — and scheduling tools use it to publish queued posts at the time you choose. The API itself is free, and unlike Instagram’s, it accepts text-only posts.

The numbers that shape a Threads calendar

The culture is the real constraint

Everything imported from Instagram muscle memory misfires on Threads. The hashtag wall becomes one topic tag — the platform literally accepts a single one. The polished announcement underperforms the open question. And the reply counts for more than the post: Threads distributes conversation, which is presumably why the API’s reply quota is four times its posting quota. Schedule the posts; show up live for the replies.

The scheduling workflow

• 1. Connect Threads directly. Threads authorises through its own login and its own permissions — a proper OAuth screen, no password handed to anyone.
• 2. Write for the 500, not down to it. If you run the write-the-core-first workflow from posting to every network at once, your Threads version is the core plus one question.
• 3. Queue at conversation hours. Threads is a phone-in-hand network; schedule where replies can happen, because the algorithm feeds on them.
• 4. Route the replies somewhere you’ll see them. Replies are first-class objects in the API, which is why a shared inbox can collect them next to your other networks’ comments.

One honest expectation about Threads analytics

If your scheduler’s dashboard shows a Threads follower count that trails the app — including a flat zero on a new account — that is currently Meta’s bug, not the tool’s: the follower metric is a daily rollup that under-reports small accounts, while other metrics in the same API response return correctly. We documented it, with the receipts, in why your numbers don’t match the native apps.

The mistakes that waste the head start

• Treating it as an Instagram caption mirror. Same company, opposite culture — text-first, one tag, question-shaped.
• Link-dumping every post. Links are allowed and unfurl fine, but a feed of pure link posts reads as syndication, and syndication earns no replies.
• Scheduling the posts and ghosting the replies. On the network whose API gives you 4× the quota for replying, silence is the expensive part.
• Waiting for it to feel established. The reason to build a Threads habit now is precisely that most brands haven’t — the feed has room, and early consistency compounds.