Threads API: Publish and Schedule Posts with the Threads Publishing API

A threads api lets an app publish and schedule posts to Meta's Threads on a creator's or business's behalf, instead of a person posting from the Threads app. IMMA AI's threads api integration checks the account's remaining daily quota before queuing a post, and schedules or publishes it alongside TikTok, Instagram and Facebook Pages from the same request.

What is the Threads API?

The Threads API is a separate product from the rest of Meta's Graph API: it uses its own app ID and app secret, tied to a dedicated Threads use case in Meta's developer console, rather than sharing credentials with a Facebook or Instagram app. The core permission is threads_basic, required for any access at all, with threads_content_publish needed to post, and threads_read_replies, threads_manage_replies and threads_manage_insights covering replies and analytics. A Threads access token is long lived, valid for 60 days, and can be refreshed before it expires rather than requiring the user to reconnect. IMMA AI's threads api integration (preview) requests only the permissions a screen in the dashboard actually uses, since Meta's app review checks that every requested permission is visibly exercised in the product, and refreshes tokens automatically in the background so a connected account does not silently stop posting after 60 days.

Can you schedule posts on Threads through the API?

Yes, in the same way as Instagram: the Threads API itself publishes a container immediately once called, it does not accept a future timestamp directly, so scheduling is a layer IMMA AI adds on top. A post created with a future scheduled_at value is validated and stored, and IMMA AI calls the Threads API to create and publish the container at the scheduled time. This works through a single POST /posts call or through POST /posts/batch, which accepts up to 31 items in one request so an AI agent or a person can queue a week or a month of Threads posts at once, with each item validated on its own rather than the whole batch failing together. A GET /threads_publishing_limit style quota check happens before an item is queued, not only at publish time, so a post that would exceed the daily limit is rejected early with a clear message instead of failing silently when its scheduled time arrives.

What are Threads API posting limits?

Threads enforces separate daily limits for three kinds of activity, all reset on a rolling 24 hour basis: up to 250 posts, up to 1,000 replies, and up to 100 deletes per account. The Threads API exposes a GET /threads_publishing_limit endpoint specifically so an app can check how much of that quota remains before attempting another action, rather than discovering the limit only after a request fails. IMMA AI's threads api integration calls this endpoint as part of its own quota check, so a post queued through IMMA AI is checked against the same numbers Threads itself would enforce. Because access tokens last 60 days, IMMA AI also tracks token expiry per connected account and triggers a refresh well before that window closes, which matters for any workspace that schedules Threads content far enough in advance that a token could otherwise expire mid queue.

Threads API limits at a glance

Limit	Value
Posts per account per 24 hours	250
Replies per account per 24 hours	1,000
Deletes per account per 24 hours	100
Access token lifetime	60 days (refreshable)
Quota check endpoint	GET /threads_publishing_limit

How it works

IMMA AI checks the Threads publishing limit before queuing a post, then creates and publishes the container directly or at a scheduled time. See the social media API page for how Threads fits alongside TikTok, Instagram and Facebook Pages, or Instagram posting API for the closely related Instagram flow.