Threads · threads-posts

Threads posts scraper API

Threads posts from users, a keyword search or a thread: text, likes, replies, reposts, views, media, date.
ThreadsWeblovelyjsoninput"mode": "posts""usernames": ["zuck"]"maxItems": 10
Price
$0.0045 / post
Results per run
10 default · up to 100
Billing
Only results delivered are billed. Failed runs pay no call fee.

Hand it to your AI agent

Copy this prompt into Claude Code, Cursor, Codex or any coding agent. It tells the agent where the docs are and how to use your API key.

Use the Lovely Router data tool "Get Threads posts" (id `threads-posts`, Threads) to get data for me. It returns JSON.

- Docs (read first): https://lovelyrouter.com/docs/tools/run.md and https://lovelyrouter.com/docs/api/tools.md
- Input fields and price: GET https://lovelyrouter.com/v1/tools/threads-posts (public, no key needed). Price: $0.0045 / post.
- Run: POST https://lovelyrouter.com/v1/tools/threads-posts/run with a body like `{"input":{"mode":"posts","usernames":["zuck"],"maxItems":10},"max_results":10}`. A 200 has the finished run with `items`; a 202 means it is still running, so poll the `poll` path until `status` is `succeeded`, `failed`, `timed_out` or `stopped`.
- Only delivered results are billed. Keep max_results small on the first run, check the output, then scale up (up to 100 per run).
- If you support MCP, you can instead connect the server https://lovelyrouter.com/mcp (Streamable HTTP, same key; https://lovelyrouter.com/docs/tools/mcp.md) and use suggest_tools, get_tool and run_tool with tool "threads-posts".
- Auth: read my API key from the LOVELY_API_KEY environment variable and send it as `Authorization: Bearer $LOVELY_API_KEY`. Never print or commit the key. If it is not set, ask me to create one at https://lovelyrouter.com/app/keys.
- Billing is prepaid: every call is charged to my balance, so test with a small request before running anything large.
- Every docs page is plain Markdown; the full index is https://lovelyrouter.com/llms.txt.

My task: <describe the data you need, e.g. which places, profiles, keywords or URLs, and the output format>

Input

modestringrequired

Posts — an account's own posts, as many as you ask for. Replies / Reposts — what an account answered or boosted. Profile — followers, bio, links and contacts. Search — public posts for keywords and hashtags. Thread — one post with its replies. Accounts — people and brands matching a keyword.

posts · replies · reposts · profile · search · thread · users

usernamesarray

For Posts, Replies, Reposts and Profile. Bare name, with @, or the profile URL: zuck, @natgeo, https://www.threads.net/@nasa.

keywordsarray

For Search and Accounts. AI agents, #nba, coffee roaster brooklyn. The # is optional.

postUrlsarray

For Thread mode: https://www.threads.net/@zuck/post/Dcy_A8pGo-m. Share links from the app (https://www.threads.com/share/CODE) work too. In Posts mode these are fetched too.

postedAfterstring

YYYY-MM-DD. Older posts are dropped and Posts mode stops paging once it reaches them.

postedBeforestring

YYYY-MM-DD. Newer posts are dropped. Together with Posted after this gives a date window, so a scheduled run never re-collects yesterday's posts.

maxItemsinteger

Stop after this many rows in the run.

Try it

Costs at most $0.045
Sign up to run
curl https://lovelyrouter.com/v1/tools/threads-posts/run \
  -H "Authorization: Bearer $LOVELY_API_KEY" \
  -H "content-type: application/json" \
  -d '{"input":{"mode":"posts","usernames":["zuck"],"maxItems":10},"max_results":10}'
# MCP (agents): suggest_tools → get_tool → run_tool
run_tool({
  "tool": "threads-posts",
  "input": {"mode":"posts","usernames":["zuck"],"maxItems":10},
  "max_results": 10
})

What it costs

ResultsRuns (at 100 per run)Cost
1001$0.45
1,00010$4.50
10,000100$45.00

Prepaid, no subscription. Fewer results than requested cost less. Pricing

Used for

Frequently asked questions

How much does the Get Threads posts API cost?

$0.0045 / post. 1,000 results, fetched in runs of up to 100, cost $4.50. There is no subscription: you pay from a prepaid balance.

Is this a Threads scraper?

Yes. If you searched for a Threads scraper, a Threads API or a meta Threads data extractor, this is it: Threads posts from users, a keyword search or a thread: text, likes, replies, reposts, views, media, date.

How many results does one run return?

10 by default and up to 100 per run. Set max_results to cap a run: you are billed only for the results it delivers.

Do I need a Threads account or API key?

No. You call the tool with your Lovely Router API key and get JSON back. There is nothing to set up on Threads.

Can an AI agent use this tool?

Yes. Connect Claude Code, Cursor or any MCP client to the Lovely Router MCP server: the agent finds the tool with suggest_tools and runs it with run_tool and the id threads-posts.

What happens if a run fails?

A run that fails or is stopped pays only for the results it delivered, with no call fee. The most a run can cost is held when it starts and the rest is released when it settles.

Related tools