TL;DR: You can auto post to Threads, but not the way most people expect. Meta opened a real Threads API in June 2024, and it’s free to use, no per-call fee like X charges. The catch is that publishing through it means registering as a Meta developer, building an app, and clearing App Review for the
threads_content_publishpermission, not something a single creator does just to post from their own account. The faster route for one account is driving the browser session you already post from.
Threads crossed 500 million monthly active users in June 2026, according to Meta’s own announcement, and it still ships without the one thing every other major platform gives creators by default: an easy way to let something else post for you. X sells API access by the call. LinkedIn gates its posting API behind a Community Management application. Threads has an API too, but reaching it takes a different kind of patience: not a credit card, a review queue.
Why “auto post to Threads” isn’t a one-line answer
Meta opened the Threads API to third-party developers in June 2024, letting apps publish text, image, and video posts through official endpoints instead of scraping the app. That part is straightforward. What trips people up is who counts as a “developer” here.
To call the publish endpoint, you register an app in Meta’s developer console, request the threads_content_publish permission, and submit that request for App Review, the same process Meta uses to vet apps touching Instagram and Facebook data. Each permission goes through its own review, and reviewers expect a screencast of the exact flow your app uses it for. That’s a reasonable bar for a company building a scheduling product for thousands of users. It’s a strange one to clear just so your own Threads account can post itself.
Once an app is approved, the API is genuinely free: no monthly fee, no per-post charge, a real difference from X’s metered API pricing. But it does cap you. Threads limits every profile to 250 original posts, 1,000 replies, and 100 deletions inside any rolling 24-hour window, on top of a 250-calls-per-user-per-hour ceiling. You can check your own usage anytime by calling the threads_publishing_limit endpoint, which returns exactly how much of each quota you’ve used.
Threads also picked up a basic in-app scheduler, first tested in December 2024, that lets you tap the three-dot menu on a draft and queue it for later. It’s useful for a single post and does nothing for the actual job of running an account: it can’t decide what to post, can’t reply to a comment, and reporting on how consistently it’s rolled out to every account type still varies.
Let an AI run it through your own logged-in session
This is where PublishPort’s model skips the App Review queue entirely. Instead of registering an app and asking Meta for permission to post on your own behalf, PublishPort gives an AI agent two tools: list_capabilities(), a plain-language list of what’s available per platform, and local_bash(cmd), which runs the actual publish command through opencli, an open-source CLI that drives the browser session you’re already logged into. Nobody reviews an app, because nothing is calling Meta’s developer API at all.
Concretely, the Threads adapter (publishport-opencli, currently pinned at 1.0.17) waits for the post composer to render in your real browser tab, types the text into it, and then polls the page to confirm the text actually landed before it calls the post sent. If you’re not logged into Threads, it doesn’t try to log in for you: it checks for the session cookie Threads shares with Instagram, and if that cookie is missing, it throws an authentication error instead of silently failing. That’s the same underlying approach covered in what breaks when the agent lives in the cloud instead of your machine, and Threads is one of the platforms it now reaches, alongside the fediverse trio covered in cross-posting to X, Threads, Bluesky, and Mastodon. The free client download is what a cloud AI connects to when it runs that command.
How to actually set it up
- Install the PublishPort desktop client and confirm it can see your machine’s browser profiles.
- Log into Threads normally, in the same browser session the client will use, so the session cookie is already there.
- Point your AI agent at the client through its MCP endpoint or the paid relay, then have it call
list_capabilities()to confirm Threads shows up as postable. - Give the agent a draft and let it call the publish command. It writes into the same composer you’d use by hand and verifies the text landed before reporting success.
- Watch the first few posts land manually until you trust the flow, the same way you’d trust any new hire before handing over the keys.
Limits and what to keep in mind
Nothing here removes Threads’ own rules. Posting 250 times in a day is still 250 times in a day as far as the platform’s abuse systems are concerned, and duplicate or near-identical posts across accounts read the same whether a human or an AI sent them. Keep the pace something an active human account would plausibly hit, don’t blast the same text to multiple Threads profiles at once, and treat the session cookie your AI is using like any other credential: if it leaks, whoever has it can post as you. None of this guarantees an account never gets flagged. It just means the automation isn’t the thing doing the flagging.
Auto-posting to Threads checklist
- Confirm whether you actually need Meta’s official API (multi-account SaaS, analytics dashboards) or just want your own account posting on autopilot
- If it’s the official API: register a Meta developer app, request
threads_content_publish, budget weeks for App Review - If it’s your own account: skip the review queue and drive your existing logged-in session instead
- Either way, respect the 250-post daily ceiling and Threads’ own spam and duplicate-content rules
- Never share your session cookie or API token outside the tool that needs it
FAQ
Does Threads have an API?
Yes. Meta opened the Threads API to third-party developers in June 2024, covering publishing, replies, and insights. Using it to post on your own account’s behalf still requires registering a Meta developer app and clearing App Review for the publish permission, which is built for companies shipping a product, not a single creator automating their own feed.
Is the Threads API free?
Yes, there’s no published paid tier or per-call fee, unlike X’s metered pricing. The cost isn’t money, it’s the App Review process: each permission needs its own review and a demo of the exact flow your app uses it for, which typically takes weeks.
What’s the Threads posting limit per day?
Threads caps every profile at 250 original posts and 1,000 replies inside any rolling 24-hour window, along with a 100-deletion cap and hourly call limits. You can check your own real-time usage against these caps through the threads_publishing_limit endpoint if you’re building on the official API.
Can you schedule posts on Threads?
Threads added a basic in-app scheduler, first tested in December 2024, accessible from the three-dot menu on a draft. It queues one post at a time for later; it doesn’t generate content, reply to anything, or connect to Meta Business Suite the way Instagram and Facebook scheduling do.
Will auto-posting to Threads get my account flagged?
It’s the posting pattern that gets flagged, not the automation itself. Duplicate content across accounts, posting faster than a human plausibly would, and ignoring Threads’ own spam rules are what trip enforcement, whether the post came from a script or a person typing fast.
Do I need a business account to use Threads automation tools?
Only if you’re going through Meta’s official API and Business Suite-adjacent tooling, which is built around professional accounts. Tools that drive your own logged-in browser session work with whatever account you’re already signed into, personal or professional.