Threads API Rate Limits: 250 Posts a Day, and a Ceiling That Shrinks When Nobody Reads You
- Official Threads API quotas per rolling 24 hours: 250 published posts, 1,000 replies, 100 deletions, 500 location searches.
- A second, stranger limit: "Calls within 24 hours = 4800 * Number of Impressions" — your API budget is derived from how many people saw your content.
- That makes it a negative feedback loop for new profiles: low reach yields a low call budget, which limits the activity that would build reach.
- These numbers govern API publishing, not tapping "post" in the app. Any article that says "Threads limits you to 250 posts a day" has confused the two.
Most platform limits reach you as a wall: something stops working and you go looking for why. The Threads API is unusual — Meta writes its numbers down, in public, in a document your scheduling tool reads every single day and never shows you.
Here they are.
The four numbers Meta publishes
From the official Threads API documentation, all measured over a rolling 24-hour window rather than a calendar day:
- Posts: 250. "Threads profiles are limited to 250 API-published posts within a 24-hour moving period."
- Replies: 1,000. "Threads profiles are limited to 1,000 replies within a 24-hour moving period."
- Deletions: 100. "Threads profiles are limited to 100 deletions within a 24-hour moving period."
- Location searches: 500 in the same window.
"Rolling" is the word doing the quiet work. There is no midnight reset that wipes the slate. If you burned 250 posts between 2pm and 6pm yesterday, capacity comes back gradually across that same stretch today — not all at once. This is why "I'll just wait until tomorrow" so often fails: tomorrow, in this system, is not a thing.
Four to one is the ratio worth noticing: 1,000 replies against 250 posts. Meta priced conversation four times cheaper than broadcasting, and that is a statement about what the platform wants from you.
The limit almost nobody has read: your ceiling is derived from your reach
Underneath the fixed quotas sits a formula, and it is the most consequential line in the entire document:
"Calls within 24 hours = 4800 * Number of Impressions", where impressions reflect how far your content travelled in the previous 24 hours.
Read that again with a new profile in mind. Your allowance of API calls is a multiple of how many people saw you. Low impressions, small budget. A brand-new profile with almost no reach gets almost no room to operate — which constrains precisely the activity that would earn reach in the first place.
This is a genuine negative feedback loop, and it is worth naming plainly because it gets misdiagnosed constantly. When a new Threads profile starts throwing errors after a modest burst of automated activity, the reflex explanation is "shadowban". The documented explanation is duller and much more actionable: your call budget is proportional to a number that starts near zero.
Why "Threads limits you to 250 posts a day" is wrong
This is the single most common mistake in write-ups of these numbers, and it is worth being precise about because it changes what you should do.
Every figure above governs API-published activity: content pushed through Meta's developer interface by an app that holds your token. Opening the Threads app on your phone and typing something is a different path entirely, and these quotas are not what governs it.
So the practical translation is:
- If you post by hand, these numbers are not your ceiling and never were.
- If you use any scheduler, bulk poster, cross-poster, or automation platform that connects to Threads, these are exactly your ceiling — shared across every tool holding a token for that profile.
- That last clause catches people out. Two tools connected to one profile draw from one budget. The second tool did not get its own 250.
What to actually do with this
Three things, in order:
1. Classify your failures instead of feeling them. Publishing failures land in three buckets — over quota, insufficient permission, and content rejected. Only the first one is fixed by waiting, and it needs you to wait into the rolling window, not until tomorrow. The other two never resolve by retrying, and retrying them is how people burn a day.
2. Count your tokens, not your tools. Before adding a second automation to the same profile, remember that both draw on one allowance. The failure will surface in whichever tool happens to run second, which makes it look like that tool is broken.
3. Treat the reply budget as the real one. With 1,000 replies against 250 posts, the API is telling you where the room is. On a conversation-shaped platform that also happens to be where reach comes from. We went deeper into what Threads is actually optimising for in The Threads Algorithm in 2026, and into diagnosing a quiet profile in Why Are My Threads Not Getting Views?.
The route that sidesteps the quota entirely
There is a structural point buried in all of this. Every quota above exists because your content passes through Meta's developer interface. Some tools do not take that route at all.
NoobClaw is one of them: it runs as a desktop application on your own machine and publishes through your own logged-in browser session in a fingerprint-isolated profile, rather than through a platform API on a server somewhere. There is no developer app, no token, no app-review status — and therefore no API quota of this kind in the picture. The honest trade-off is equally structural: your machine has to be running and your login has to be valid, which a cloud scheduler does not require. Neither approach is universally better. But if the thing that keeps breaking your week is an API quota you cannot see, it is worth knowing the other shape exists. Related reading: Social Media Automation vs Scheduling.
A quick reference you can keep
Four lines worth writing down somewhere you will find them again at 2am:
- 250 / 1,000 / 100 / 500 — posts, replies, deletions, location searches, each per rolling 24 hours, per profile.
- Rolling, not daily. Capacity returns in the same shape it was spent. If you emptied it in a burst, it comes back as a burst, a day later.
- 4,800 × impressions — your total call budget. Small account, small budget, and no appeal process because nothing is wrong.
- One profile, one budget, however many tools hold a token for it.
And one line that is not a number: if your Threads activity is failing and your profile has meaningful reach, you are almost certainly not over quota — 250 posts a day is a lot of posts. Look at permissions and content rejections first. If your profile has almost no reach, invert that: check the call budget before anything else.
FAQ
Is the Threads API free to use?
Meta's overview page for the Threads API sets out permissions and quotas rather than a price list, and does not state a fee for API access itself. What it does set out clearly are the constraints: the rolling 24-hour quotas above and the impressions-derived call budget. Treat "free" and "unlimited" as separate questions — the second one has a published answer, and it is no.
Do the 250 posts reset at midnight?
No. The documentation specifies a "24-hour moving period", which means capacity returns gradually as your earlier activity ages out, not in one block at a fixed hour. Planning around a midnight reset will produce failures you cannot explain.
Why does my brand-new Threads profile hit limits so fast?
Because of the second formula: your 24-hour call allowance is calculated as 4,800 multiplied by your impressions over the previous 24 hours. A new profile has very little reach, so it has very little allowance. It reads like suppression and is actually arithmetic — which matters, because the fix is building reach, not filing an appeal.