Developer & Agents•
5 min read
•
2026-11-16 · Updated 2026-11-16

Threads API Guide (2026): Post, Tokens, Rate Limits and Scheduling

TL;DR — Direct Answer

Yes. Meta's official Threads API publishes text, image and video posts in two calls on graph.threads.com: POST /{threads-user-id}/threads creates a container, then POST /{threads-user-id}/threads_publish posts it. You need threads_basic and threads_content_publish, a 60-day refreshable token, and must stay within 500 characters, 250 posts per 24 hours and 5 links.

By Reeling Team. Examples describe the documented implementation; no live publishing test is implied.

Does Threads have an API, and is it free?

Yes. Meta opened the official Threads API to all developers on June 18, 2024, and the docs we read on November 16, 2026 list no usage fee or paid tier, only quotas such as 250 posts per profile per 24 hours. Posting for people who are not your app's testers needs App Review.

Last verified: November 16, 2026, against the Meta pages in Sources.

What you needValueMeta page
Base URLhttps://graph.threads.com/v1.0 (graph.threads.net also works)Overview
Two callsPOST /{threads-user-id}/threads, then POST /{threads-user-id}/threads_publish with creation_idPosts
Permissionsthreads_basic plus threads_content_publishPosts
Limits500 characters (emoji count as UTF-8 bytes), 5 links, 250 posts per rolling 24 hoursPosts, Overview

How do I get a Threads API access token and how long does it last?

Send the user through Threads' authorization window, exchange the one-hour, single-use code for a short-lived token, then swap that for a long-lived token with grant_type=th_exchange_token. A long-lived token lasts 60 days and can be refreshed once it is at least 24 hours old, so run a scheduled refresh job.

Use the Threads app ID and secret, not the main app ID, and keep the secret server side.

StepCall on graph.threads.comResult
Code to short-lived tokenPOST /oauth/access_token with grant_type=authorization_codeValid 1 hour
Short-lived to long-livedGET /access_token with grant_type=th_exchange_tokenValid 60 days
RefreshGET /refresh_access_token with grant_type=th_refresh_tokenToken must be 24 hours old; valid 60 days again

How do I post to Threads with the API?

Call POST /{threads-user-id}/threads with media_type set to TEXT, IMAGE or VIDEO plus your text or public media URL to create a container, then call POST /{threads-user-id}/threads_publish with that container's id as creation_id. Meta advises waiting about 30 seconds before publishing a media container. Text is limited to 500 characters.

Check clip dimensions and caption length first, then run these four calls in order, copying the container id from the create response into CONTAINER_ID. We ran them only against a local mock.

H=https://graph.threads.com/v1.0
curl -s "$H/$USER_ID/threads_publishing_limit?fields=quota_usage,config&access_token=$TOKEN"
curl -s -X POST $H/$USER_ID/threads -d media_type=TEXT --data-urlencode "text=Hello from the Threads API" -d access_token=$TOKEN
# video: media_type=VIDEO and video_url; poll this once a minute until FINISHED
curl -s "$H/$CONTAINER_ID?fields=status,error_message&access_token=$TOKEN"
curl -s -X POST $H/$USER_ID/threads_publish -d creation_id=$CONTAINER_ID -d access_token=$TOKEN

What are the Threads API rate limits?

Each Threads profile can publish 250 API-published posts, send 1,000 replies and make 100 deletions in any rolling 24 hours, and a carousel counts as one post. Separately, an app's call count is capped at 4,800 times the number of impressions per 24 hours, with impressions floored at 10.

Read GET /{threads-user-id}/threads_publishing_limit?fields=quota_usage,config before each publish; quota_total is 250.

Can I schedule Threads posts through the API?

Not natively. The Threads publishing reference lists no scheduling or publish-time parameter, and the changelog through August 18, 2026 has no scheduling entry. Your app keeps the queue, creates the container shortly before the due time, publishes at the due time and enforces the 250-post quota itself.

WhenWhat your scheduler doesWhy
On schedulingStore text, media URL and due time; no container yetContainers expire after 24 hours
Due time minus 6 minutes (video)Check quota, create container, poll status once a minute, at most 5 timesOur schedule, from Meta's wait and polling advice
Due timePOST threads_publish once; if it times out, read the container statusPUBLISHED means it already posted

Threads API errors and how to fix them

These rows come from Meta's troubleshooting, posts and token pages.

SymptomCauseFix
THREADS_API__LINK_LIMIT_EXCEEDEDMore than 5 unique links (enforced since December 22, 2025)Cut links; a link_attachment repeating a text URL counts once
Calls fail after 60 daysLong-lived token not refreshed within 60 daysRefresh once it is 24 hours old, well before day 60
Container ERROR or EXPIREDMedia processing failed, or no publish within 24 hoursCheck the public URL and media specs; create a new container
Works for you, not customersWithout advanced access only Threads testers can be posted forAdd testers, or pass App Review and publish the app

Build on the Threads API or use a scheduler API?

Build directly on Meta's API when you need text-only, image, carousel, poll or GIF posts, or full control of review and tokens. Use a scheduler API when you mainly queue video posts across networks and want to skip the Meta app, token jobs and queue. Reeling's Threads support is video container publishing.

NeedMeta's Threads APIReeling REST API v1 or MCP
Review and tokensYou build the app, App Review and a refresh jobAuthorize once in Connect Channels; development-mode accounts may need tester access
Post typesText, image, video, carousel, polls, GIFsVideo up to 100 MiB (MP4 or MOV), text up to 500 characters

Frequently Asked Questions

Does Threads have an API, and is it free?

Yes. Meta's official Threads API has been open to all developers since June 18, 2024. Meta's docs list no usage fee, only limits such as 250 posts per rolling 24 hours.

How long does a Threads API access token last?

A short-lived token lasts 1 hour and a long-lived token 60 days. Refresh a long-lived token with grant_type=th_refresh_token once it is 24 hours old and before it expires.

Can I schedule Threads posts through the API?

Not natively: Meta's publishing reference has no scheduling parameter. Keep your own queue and enforce the 250-post quota yourself; a scheduler API such as Reeling's accepts scheduled_for.

Sources and related documentation

Schedule Threads video posts through one API

Authorize Threads in Reeling, create an API key, then send scheduled_for.

Read the REST API reference
Account requirements apply