Threads user timeline API
Parameters from the 2026-10-25 specification snapshot; response rows checked against live responses on 2026-11-21
Quick answer
POST /threads/users/task with author_id (the Threads username; a leading @ is optional) and an optional start_date and end_date starts an asynchronous task that collects that public account's posts. Poll GET /threads/users/task/{task_id}: the posts are returned in data with total_count, each with its URL, native post ID, text, timestamps, like, reply and share counts and media URLs. Data is collected by web crawlers from content publicly published on Threads.
What teams use it for
- Follow what the official account of a brand, media outlet or institution published over a period.
- Keep a dated record of a public account's posts for research.
- Compare posting activity and engagement across several accounts in the same date window.
Endpoints
Base URL: https://api.infominer.io/api/v2. Send your API key in the auth-header request header.
| Method | Path | What it does |
|---|---|---|
| POST | /threads/users/task |
Creates a public account timeline task with an optional date range. |
| GET | /threads/users/task/{task_id} |
Polls a timeline task: status, counters, and the account's posts in data. |
Request parameters
POST /threads/users/task
| Parameter | In | Type | Required | Default / allowed | Description |
|---|---|---|---|---|---|
author_id |
body | string | Yes | Threads username of the public account; a leading @ is optional. | |
end_date |
body | string | No | End of the date range, inclusive (YYYY-MM-DD). Ignored if start_date is missing. | |
mask_author |
body | boolean | No | false |
Set to true to remove author identity fields from this response. Send it on each GET poll to mask the returned rows. |
max_scroll |
body | integer | No | Scroll limit for the crawl. Integer. | |
rerun |
body | boolean | No | Boolean; run the collection again. | |
start_date |
body | string | No | Start of the date range, inclusive (YYYY-MM-DD). |
GET /threads/users/task/{task_id}
| Parameter | In | Type | Required | Default / allowed | Description |
|---|---|---|---|---|---|
task_id |
path | string | Yes | Task ID returned when the task was created. | |
mask_author |
query | boolean | No | false |
Set to true to remove author identity fields from this response. Send it on each GET poll to mask the returned rows. |
Response fields
| Data | Fields | Endpoint |
|---|---|---|
| Public account posts | id, post_id, url, author, author_id, author_name, content, tm, tm_crawler, like_count, reaction_count, comment_count, share_count, is_reply, is_quote, metadata_img, metadata_videos, tag, source | GET /threads/users/task/{task_id} |
Code examples
curl: create the task
curl -X POST https://api.infominer.io/api/v2/threads/users/task \
-H "auth-header: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"author_id": "sample_user_1", "start_date": "2026-06-01", "end_date": "2026-06-30"}'
curl: poll the task by ID
curl "https://api.infominer.io/api/v2/threads/users/task/$TASK_ID?page=1&per_page=1000" \
-H "auth-header: YOUR_API_KEY"
Python (requests): create, poll, read
import time
import requests
BASE_URL = "https://api.infominer.io/api/v2"
HEADERS = {"auth-header": "YOUR_API_KEY"}
# 1. Create the task
resp = requests.post(
f"{BASE_URL}/threads/users/task",
headers=HEADERS,
json={
"author_id": "sample_user_1",
"start_date": "2026-06-01",
"end_date": "2026-06-30",
},
timeout=30,
)
resp.raise_for_status()
task = resp.json()
# 2. Poll until the task leaves INIT / RUNNING
for _ in range(120):
resp = requests.get(
f"{BASE_URL}/threads/users/task/{task['id']}",
headers=HEADERS,
params={
"page": 1,
"per_page": 1000,
},
timeout=30,
)
resp.raise_for_status()
result = resp.json()
status = result.get("status") or result.get("task", {}).get("status")
if status not in ("INIT", "RUNNING"):
break
time.sleep(15)
else:
raise SystemExit("task still running; poll it again later")
if status == "FAILED":
raise SystemExit("task failed")
if status != "DONE":
print("task ended with status", status, "- results may be incomplete")
# 3. Read the records (use page / per_page to fetch further pages)
for row in result.get("data", []):
print(row.get("url"), (row.get("content") or "")[:60])
Sample response
Illustrative data written by hand: accounts are sample_user_n and IDs are obviously fake. Field names follow live API responses checked on 2026-11-21; the sample shows a subset of the fields.
Poll response once the task is DONE (illustrative data)
{
"id": "00000000-0000-4000-8000-000000000001",
"status": "DONE",
"author_id": "sample_user_1",
"start_date": "2026-06-01",
"end_date": "2026-06-30",
"total": 2,
"completed": 2,
"partial": false,
"timed_out": false,
"failed_articles": 0,
"failed_pages": 0,
"total_count": 2,
"data": [
{
"id": "00000000-0000-4000-8000-000000000003",
"source": "threads",
"post_id": "00000000001",
"url": "https://www.threads.com/@sample_user_1/post/00000000001",
"author": "sample_user_1",
"author_id": "0000000001",
"content": "週末走了一條不太熱門的步道,沿途視野很開闊,建議早點出發避開人潮",
"tm": 1781056800,
"tm_crawler": 1781143200,
"like_count": 34,
"reaction_count": 34,
"comment_count": 2,
"share_count": 1,
"is_reply": false,
"is_quote": false,
"metadata_img": [],
"metadata_videos": [],
"tag": ""
},
{
"id": "00000000-0000-4000-8000-000000000006",
"source": "threads",
"post_id": "00000000004",
"url": "https://www.threads.com/@sample_user_1/post/00000000004",
"author": "sample_user_1",
"author_id": "0000000001",
"content": "整理了這個月走過的三條步道,交通方式和所需時間都寫在清單裡",
"tm": 1781229600,
"tm_crawler": 1781316000,
"like_count": 12,
"reaction_count": 12,
"comment_count": 0,
"share_count": 2,
"is_reply": false,
"is_quote": false,
"metadata_img": [],
"metadata_videos": [],
"tag": ""
}
]
}
Limits and notes
- author_id is required; start_date and end_date are optional and inclusive.
- Poll responses are paginated: send page and per_page on the GET request (per_page defaults to 1000, the maximum). Each response reports page, per_page and total_count, the number of rows collected so far; read further pages until you have total_count rows.
- If you pass end_date without start_date, the upstream ignores it and applies its default range.
- Only content publicly published on Threads is collected.
- How far back timelines go and refresh frequency are confirmed per project scope.
More Threads API pages
- Keyword search
- Replies
- User timeline
- Reactions
Request a trial
In the request form below, mention Threads and tell us the keywords or accounts, whether you need replies and reactions, and whether author fields should be masked. We confirm the scope and reply with the arrangements for the trial and API key.
Fill in the form to request a trial. We confirm the scope and reply with trial and integration arrangements.
Fill in the request formFAQ
- What do I pass as author_id?
- The account's Threads username, with or without the leading @.
- Can I collect posts from a private account?
- No. Only content publicly published on Threads is collected.
- Does the timeline include the replies to each post?
- The timeline task collects the account's posts. To collect the replies to a post, create a reply task with that post's URL.
- How is the data collected? Is this the official Threads API?
- By web crawlers, from content publicly published on Threads. LargitData is not affiliated with Meta or Threads, and this is not Meta's Threads API. Whether this suits your use depends on the purpose and jurisdiction and is for your legal team to assess; we can provide a description of sources and collection methods.