Threads API rate limits and access tokens, explained
The Threads API limits from Meta's docs: 250 posts, 1,000 replies, and 100 deletions per profile per 24 hours, call limits that scale with impressions, and 1-hour and 60-day tokens. How to check your quota and refresh tokens.

On this page
You are posting to Threads from your own code and want to know how much you can publish, how many calls you can make, and why your token stopped working after a while. Meta documents three kinds of limits: publishing limits per profile, call rate limits per app, and token lifetimes. Here are the numbers from Meta's Threads API docs, how to check where you stand, and what changes if you post through eksis instead.
The short answer
- Posts: 250 API-published posts per Threads profile in a 24-hour moving period. A carousel counts as one post.
- Replies: 1,000 replies per profile per 24 hours. Deletions: 100 per 24 hours.
- Check your usage with
GET /{threads-user-id}/threads_publishing_limitand the fieldsquota_usage,config. - Call rate limits scale with impressions: calls within 24 hours = 4,800 × the number of impressions, with a minimum of 10 impressions.
- Tokens: a short-lived token lasts 1 hour; a long-lived token lasts 60 days and can be refreshed once it is at least 24 hours old and before it expires.
- Through eksis: eksis holds and refreshes the tokens. Free publishes up to 50 posts per Threads profile per 24 hours; paid plans follow Meta's 250.
Publishing limits
Meta's Threads docs set three quotas per Threads profile, each over a 24-hour moving period:
| Action | Limit per 24 hours |
|---|---|
| API-published posts | 250 |
| Replies | 1,000 |
| Deletions | 100 |
Posts are also limited in shape: text posts up to 500 characters, and carousels with 2 to 20 items.
Check your quota
The threads_publishing_limit endpoint returns how much of each quota a profile has used:
curl -G "https://graph.threads.net/v1.0/THREADS_USER_ID/threads_publishing_limit" \
-d "fields=quota_usage,config" \
-d "access_token=ACCESS_TOKEN"
The response looks like this:
{
"data": [
{
"quota_usage": 4,
"config": {
"quota_total": 250,
"quota_duration": 86400
}
}
]
}
For replies, ask for reply_quota_usage,reply_config; for deletions, delete_quota_usage,delete_config. Checking before a large batch is cheaper than handling errors halfway through it.
Call rate limits
Separately from the publishing quotas, Meta counts the calls your app makes. The Threads docs give the limits as formulas over 24 hours:
- Calls = 4,800 × number of impressions
- Total CPU time = 720,000 × number of impressions
- Total time = 2,880,000 × number of impressions
Meta uses a minimum of 10 impressions in these formulas, so even a new account with almost no reach gets a working allowance. For a small account that publishes a few posts a day, the publishing quotas above are usually the limit you meet first.
Access tokens
Lifetimes
- Short-lived token: valid for 1 hour. This is what you get right after the user approves your app.
- Long-lived token: valid for 60 days. You get it by exchanging a short-lived token, as Meta's long-lived token page describes.
Refresh a long-lived token
A long-lived token can be refreshed as long as it is at least 24 hours old, has not expired, and the user has granted your app threads_basic:
curl -G "https://graph.threads.net/refresh_access_token" \
-d "grant_type=th_refresh_token" \
-d "access_token=LONG_LIVED_TOKEN"
The response contains a new token valid for 60 days. Store it and use it from then on. If a token expires, it can no longer be refreshed and the user has to authorize your app again. Meta's docs list both graph.threads.net and graph.threads.com as hosts for the API.
A simple routine that stays inside these rules: refresh each long-lived token on a fixed schedule well before 60 days, and alert yourself when a refresh fails, so you hear about a revoked permission before your next scheduled post does.
If your app gets "application does not have permission for this action" instead, the problem is permissions, not limits; see how to fix the Threads API permission error.
Post through eksis instead
If you only need to post to your own Threads profile, eksis can hold the connection for you. You connect Threads once in eksis, which uses its own approved Meta app, and eksis stores and refreshes the token, so there is no 60-day expiry for you to track. From your code you call the eksis REST API (on every paid plan) or the MCP server (on every plan, Free included) with an eksis API key instead of a Threads token.
eksis applies its own daily cap on Free: 50 posts per Threads profile per 24 hours. On paid plans eksis has no cap of its own, and Meta's 250-post limit is the only one. A post over the limit is postponed, not failed. eksis also has a daily request quota per workspace: 200 on Free (MCP only), 1,000 on Pro Eksis, and 10,000 per Super Eksis workspace.
See the Threads API page for the request that publishes a post, or compare plans.
Sources
- Meta for Developers: Threads API overview (read November 11, 2026)
- Meta for Developers: Get access tokens and permissions (read November 11, 2026)
- Meta for Developers: Long-lived tokens (read November 11, 2026)
- eksis docs: Threads platform specifications (read November 11, 2026)
Frequently Asked Questions
How many posts can I publish through the Threads API per day?
250 API-published posts per Threads profile in a 24-hour moving period, plus up to 1,000 replies and 100 deletions.
How long does a Threads access token last?
A short-lived token lasts 1 hour. A long-lived token lasts 60 days and can be refreshed once it is at least 24 hours old, before it expires.
How do I check my Threads API quota?
Call GET /{threads-user-id}/threads_publishing_limit with fields=quota_usage,config. Use reply_quota_usage,reply_config for replies and delete_quota_usage,delete_config for deletions.
What happens when a Threads token expires?
Calls fail and the token cannot be refreshed anymore. The user has to authorize your app again to get a new token, which is why refreshing on a schedule matters.


