Threads API skill

Read public Threads data as clean JSON. This Threads API skill returns a profile, a user's posts, stats for a single post, and both keyword and user search. Threads is young enough that tooling for it is thin, so a straightforward JSON read is worth more here than on the established networks.

This skill wraps 5 live Threads endpoints from the ScraperSocial API. Public data only, returned as clean JSON.

When to use this skill

• You are tracking what an account posts on Threads.
• You are monitoring a keyword or brand mention on the network.
• A user pastes a Threads post and asks about its engagement.

Do not use this skill when

• You need comments or reply threads. Threads has no comments endpoint in this API — profile, posts, stats and search only. Do not promise a reply tree you cannot fetch.
• You expect view counts. Threads does not publish every metric, so some fields other platforms expose are simply absent.
• You need to post or reply. Read-only; Meta's own Threads API covers publishing.

Setup

export SCRAPERSOCIAL_KEY=sk_live_...   # https://scrapersocial.com/app/keys

Signing up at scrapersocial.com/signup includes 100 free credits, no card required.

Permissions and scope

These scripts do exactly three things and nothing else: read one environment variable (SCRAPERSOCIAL_KEY), send HTTPS requests to https://api.scrapersocial.com (the host is a constant in the code, not configurable), and print JSON. They run as node scripts/<name>.js with no other shell use, no file writes and no persistence. call_endpoint.js accepts only the 5 documented /v1/threads/ paths in the table below and refuses anything else before a request is made.

Scripts

Every script also accepts --limit, --cursor, --fields, --format and --fresh. --limit is clamped to 50: above that the API returns an async job instead of data.

Example

node skills/threads-api/scripts/search.js "design systems"

Every response uses the same envelope:

{ "data": {}, "meta": { "count": 20, "next_cursor": "..." }, "request_id": "a18e4ef88ad4b00b" }

meta appears on paginated endpoints only. Keep request_id — support traces calls with it.

Endpoints

Costs shown per item for paginated endpoints, per call otherwise. Failed calls are not charged.

FAQ

What can I get from Threads?

Five endpoints: get_profile.js, get_posts.js, get_stats.js, search.js and user_search.js, costing 3–4 credits each.

Can I get replies to a Threads post?

No. There is no comments or replies endpoint for Threads in this API. Facebook, Instagram, YouTube, LinkedIn, Reddit, TikTok and Hacker News do have one.

Why are some engagement fields missing?

Threads does not publish everything other networks do — view counts in particular. The API returns what is public rather than estimating.

Is this an official Threads API?

No. ScraperSocial is independent and not affiliated with Meta. It returns publicly available data only.

Links

• Threads data on ScraperSocial
• All 33 platform skills
• OpenAPI spec · llms.txt

Disclaimer

ScraperSocial is an independent product and is not affiliated with, endorsed by, or sponsored by any platform named in this repository. All product names, logos and brands are property of their respective owners. These skills return only publicly available data.