Threads scraper API
Pull public Threads profiles, profile posts, single posts by URL, keyword search hits, and user search results over REST — same API key and JSON envelope as Instagram.
5 endpointsWhy teams use Social Fetch for Threads
Threads is Meta's text-first network next to Instagram. Creators reuse the same handle across both surfaces, brand mentions land in short posts that never appear as Reels, and monitoring jobs that stop at Instagram miss half the conversation. DIY scrapers for threads.net break when Meta reshuffles the web client; most enrichment stacks still treat Threads as an afterthought until a client asks why the second surface is blank.
Social Fetch exposes Threads as ordinary GET routes. You pass a handle, a threads.net permalink, or a search query and get structured JSON with `data.lookupStatus`, `meta.requestId`, and `meta.creditsCharged`. Failed upstream lookups surface as typed outcomes — not an empty 200 that looks like a deleted account.
The catalog is focused on the five lookups product teams actually schedule: profile by handle, recent posts for a handle, one post by URL, keyword post search, and people search. The same Social Fetch API key covers Instagram and the rest of the marketplace, so dual-network creator cards stay one auth story and one warehouse envelope.
What Threads data can you get?
- Profile cards by handle — bio, avatar, verification, follower count when public.
- Recent public posts for a handle (captions, metrics, media).
- Single post detail from a threads.net / threads.com permalink.
- Keyword post search with optional startDate / endDate filters.
- User search for people discovery before a full profile pull.
- Typed `lookupStatus` for found, private, and not_found outcomes.
- Same API key and `{ data, meta }` envelope as Instagram and TikTok.
Threads API endpoints
Grouped by capability from the live API catalog. Open an endpoint page for parameters and examples — credit notes come from OpenAPI pricing extensions.
Profiles & channels
1Lists & graphs
1Content
1Search & discovery
2How to call the Threads API
1. Create an API key
Sign up at Social Fetch and copy a key (`sfk_…`). New accounts get 100 free credits — enough to resolve a Threads handle, list recent posts, and run one keyword or user search against live data.
2. Call a Threads route
Start with `GET /v1/threads/profiles/{handle}` (with or without `@`), or pass a post URL to `GET /v1/threads/posts`. Send `x-api-key`. Use docs examples for search query params; use the TypeScript SDK or curl in production jobs.
3. Read the shared envelope
Branch on `data.lookupStatus` before writing rows. Log `meta.requestId` for support. Bill against `meta.creditsCharged` — that field is the source of truth for what the call cost. Join Instagram rows under the same person key when handles match.
How much does the Threads API cost?
Documented Threads routes charge 1 credit per successful completed lookup. Confirm on each operation page and with `meta.creditsCharged` — that field is the billing source of truth. Credits never expire on pay-as-you-go packs. Free signup credits apply.
Social Fetch vs the official Threads API
Meta's official Threads API (via Meta for Developers) is built for apps that act on behalf of logged-in Threads users: publishing, reply moderation, insights, and other permissions that go through Meta App Review and OAuth. It is the right tool when you manage accounts that grant your app access. It is the wrong tool when you need arbitrary public creator cards and search hits without standing up a Meta app. Social Fetch looks up publicly visible Threads pages the way a browser would — handle, URL, or query in, normalized JSON out, no creator OAuth and no Meta app review for these public read routes.
Threads API FAQ
Is there a Threads scraper API that works without Meta App Review?
Yes. Social Fetch Threads routes read public profile and content data. You authenticate to Social Fetch with an API key (`x-api-key`). You do not create a Meta Threads developer app or OAuth as the Threads user whose public data you are fetching.
How do I scrape Threads data with an API?
Create a Social Fetch key, call a documented route such as `GET /v1/threads/profiles/{handle}` or `GET /v1/threads/search?query=…`, and parse the JSON envelope. Docs include parameters, examples, and credit notes for each operation.
What Threads data does Social Fetch cover?
Five marketplace operations: profile by handle, profile posts list, single post by URL, keyword post search, and user search. Exact paths live under `/docs/api` and on this hub's endpoint list.
Profile vs profile posts vs post-by-URL — which route?
Use `GET /v1/threads/profiles/{handle}` for the identity card and follower metrics. Use `GET /v1/threads/profiles/{handle}/posts` for recent posts on that username. Use `GET /v1/threads/posts` when you already have a threads.net permalink. They are separate operations; confirm a handle with the profile GET before treating an empty feed as "no posts."
Keyword search vs user search on Threads?
`GET /v1/threads/search` finds public posts by keyword (optional `startDate` / `endDate`). `GET /v1/threads/users/search` finds people by keyword. Follow a user-search hit with the profile route when you need the full card.
How much does the Threads API cost?
You buy credit packs (or use the 100 free signup credits). Documented Threads lookups are 1 credit each on success. Always trust `meta.creditsCharged` on the response. There is no required monthly subscription for pay-as-you-go packs.
Can I use the same API key as Instagram?
Yes. One Social Fetch API key covers all marketplace platforms, including Threads and Instagram. Many teams store both under one person key; bios and follower counts still differ per network, so treat each `lookupStatus` separately.
Threads API vs the official Meta Threads API — what is the difference?
Official Threads APIs serve partner and user-authorized app use cases (publish, insights, reply management) and require a Meta app plus OAuth and App Review for production scopes. Social Fetch is a public-data lookup API: handle, URL, or query in, structured JSON out, no creator OAuth. Choose official when you need write access or private user data on accounts you manage; choose Social Fetch for public enrichment and monitoring.
Do private Threads profiles work?
Only publicly visible profiles and posts. Private or missing targets resolve through typed `lookupStatus` values (for example `private` or `not_found`) rather than inventing empty public cards.
Is scraping Threads data legal?
Social Fetch returns publicly visible data. You are responsible for how you use it under Meta's terms, applicable law, and your own compliance review. We do not give legal advice.
Start with Threads data
Create an account, spend the 100 free credits on live Threads routes, then buy a pack when the JSON fits your pipeline. Credits do not expire on pay-as-you-go packs.