Get Threads data with one API
The Threads API returns public Threads data as clean JSON.
11 active endpoints, on 1 and 2 credit tiers.
- POST/threads/v1/profile
- POST/threads/v1/posts
- POST/threads/v1/replies
- POST/threads/v1/reposts
- POST/threads/v1/post
- POST/threads/v1/post_replies
- POST/threads/v1/search
- +4 more
What Threads endpoints does ReefAPI ship?
11 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Threads API
3 of 11 endpoints, ready to run
Public Threads profile by username.
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
How the Threads API works
Threads is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 185 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Threads id shapes, and what logged-out access cannot reach
Threads reuses Instagram's id conventions, and the same post is addressable three different ways depending on which action you call. The shapes below are from live responses. The gated rows are the ones that answer with an error no matter what you pass.
| Field or action | Measured behavior | Notes |
|---|---|---|
| post id | Numeric post key, underscore, the author's numeric user id: 3971525888530486450_63269174602 | The suffix equals that author's profile.user_id. zuck's own posts end in _63055343223, which matches his profile exactly. |
| code | 11 characters, Instagram-style shortcode: DcdscDqIJSy | The /post/<code> segment. Pass code together with username, or pass the full url instead. |
| taken_at | Unix epoch in SECONDS: 1787662820 | Not ISO-8601 and not milliseconds. Multiply by 1000 before feeding a JS Date. |
| search rows | id equals the code, not the numeric key, and rows carry username, text, url and timestamp_label only | No counts and no taken_at in search output. Re-fetch a hit with the post action if you need either. |
| followers, following, likes | ok false, error code DISABLED, retryable false, detail.account_pool_required true | Logged-out Threads does not serve these lists at all. The aggregate follower_count and like_count are still available. |
| user_search | Exact or near-exact handle resolve. NOT_FOUND with 'no public Threads account resolves for ...' when nothing matches | Fuzzy people search is login-gated by Threads, so this resolves a handle rather than searching people. |
profile returns username, full_name, biography, follower_count, profile_pic_url, user_id, is_verified, is_private and, when the account has any, bio_links. There is no post count and no following count on a logged-out profile.
What people build with Threads
The jobs this data is most often used for.
endpoints
credits per call
Social analytics call profile and posts to measure a handle's reach.
Brand monitoring uses search and replies to track mentions.
Research uses reposts to gauge what spreads.
What Threads data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 185 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/threads/v1/profile \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"username":"zuck"}'import requests
r = requests.post(
"https://api.reefapi.com/threads/v1/profile",
headers={"x-api-key": REEF_KEY},
json={
"username": "zuck"
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Threads.
Get a free key →Why does the replies action return posts written by other accounts?▾
Because the Threads Replies tab renders the conversation rather than the reply alone, so the parent post travels with it. A measured replies call for zuck with limit 25 returned 25 rows, of which 12 were authored by zuck and 13 by other handles. There are two clean ways to filter: compare the row's username, or read the numeric suffix of id, which is always the author's user id.
Should I check for null or for a missing key?▾
For a missing key. This engine omits what it did not find rather than emitting null. Measured: zuck's profile has no bio_links key at all while natgeo's and instagram's do; a text-only post carries neither image_url nor video_url; and some posts arrive with no reshare_count key even though quote_count is present and set to 0. Code that reads post.reshare_count directly will throw on perfectly valid posts.
The like count changed between two calls. Which one is right?▾
Both. These are live counters read at request time. The same natgeo post returned like_count 9413 and repost_count 244 from the posts action, then 9414 and 245 from the post action seconds later. The full set is like_count, reply_count, repost_count, quote_count, plus reshare_count where Threads exposes it. Treat them as a sample with a timestamp, not as a stable key.
What comes back for a video post versus an image post?▾
media_type tells you which, and the media fields follow from it. A video post returns media_type 'video' with video_url (the mp4) and image_url (the poster frame) plus width and height; an image post returns media_type 'image' with image_url only. Carousels arrive in carousel_media[]. All media points at Meta's CDN with query parameters attached, so download the bytes if you need them later rather than storing the URL.
Why does search return posts in languages I did not ask for?▾
Because search hands back Threads' own default results page and there is no language parameter. A measured q=reef returned Japanese, Indonesian and English posts inside the same five rows. Search rows are also thinner than profile rows: no counts, no taken_at, and timestamp_label is a display string like '4d' or '03/24/25' which on one row arrived with the post header text glued onto it. Use search to find codes, then call post for anything you plan to store.
What do I get for a handle that does not exist?▾
user_search answers cleanly: ok false, NOT_FOUND, retryable false. profile is less tidy on the same input and answers PARSE_ERROR with retryable true, because it cannot distinguish 'no such user' from 'the page shape changed'. Treat a repeated PARSE_ERROR on one specific handle as 'no such account' and stop retrying. A PARSE_ERROR that hits every handle at once is the other case.
Can I see who follows an account or who liked a post?▾
No. followers, following and likes all return DISABLED with retryable false, because Threads serves those lists only to a logged-in session and this engine is public-content-only. The aggregate numbers are unrestricted: profile returned follower_count 5720868 for zuck and 18281334 for natgeo, and every post carries its own like_count.
What is the Threads API?▾
Threads API is a ReefAPI endpoint group for threads It returns live JSON through POST requests under /threads/v1.
Is the Threads API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Threads calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Threads login or account?▾
No login to Threads is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Threads data?▾
The page example is captured from a live profile call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Threads API use?▾
Threads actions currently cost 1-2 credits per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.
Can I call Threads from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call threads actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Threads API a Threads scraper?▾
It is the managed alternative to a DIY Threads scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same threads back as clean JSON.
10 Social Media APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Threads, you are one call away from the rest of the category — no second contract, no second integration.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 184 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts.