> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/threads>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/threads.mdx>

---

# Threads scraper API. Instagram's other half.

Profiles, posts and search from public Threads accounts, as JSON on the same key as Instagram. Follow an account across both apps without a second integration.

- No Meta app
- Same key as Instagram

Social Fetch exposes Threads as GET routes: profile by handle, recent posts, post by URL, keyword search, and user search. Every response includes `data.lookupStatus`, `meta.requestId`, and `meta.creditsCharged`. The same API key covers Instagram and the rest of the marketplace.

## What you can 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 endpoints

| Endpoint | Request | Credits | Docs |
| --- | --- | --- | --- |
| Profile | GET /v1/threads/profiles/{handle} | 1 credit Failed requests are free | [docs](https://www.socialfetch.dev/docs/api/v1/threads/profiles/handle/get) |
| Profile posts | GET /v1/threads/profiles/{handle}/posts | 1 credit Failed requests are free | [docs](https://www.socialfetch.dev/docs/api/v1/threads/profiles/handle/posts/get) |
| Post | GET /v1/threads/posts | 1 credit Failed requests are free | [docs](https://www.socialfetch.dev/docs/api/v1/threads/posts/get) |
| Search posts | GET /v1/threads/search | 1 credit Failed requests are free | [docs](https://www.socialfetch.dev/docs/api/v1/threads/search/get) |
| User search | GET /v1/threads/users/search | 1 credit Failed requests are free | [docs](https://www.socialfetch.dev/docs/api/v1/threads/users/search/get) |

## How to start

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.

## Pricing

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.

## Compared with the official API

Meta's official Threads API is for apps acting on behalf of logged-in users — publishing, moderation, insights — via Meta App Review and OAuth. Social Fetch looks up publicly visible Threads pages with a Social Fetch API key for public read routes.

## 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.

## Related

- [Threads Profile API](https://www.socialfetch.dev/platforms/threads/profiles-handle): Handle → card, bio, verification, and follower metrics (`GET /v1/threads/profiles/{handle}`).
- [Threads profile posts API](https://www.socialfetch.dev/platforms/threads/profiles-handle-posts): List recent public posts for a username — captions, metrics, media.
- [Threads Post API](https://www.socialfetch.dev/platforms/threads/posts): Single post by threads.net URL — caption, author, engagement, media.
- [Threads Search API](https://www.socialfetch.dev/platforms/threads/search): Keyword post search with optional date filters.
- [Threads User Search API](https://www.socialfetch.dev/platforms/threads/users-search): People discovery by keyword before a full profile pull.
- [Instagram API hub](https://www.socialfetch.dev/platforms/instagram): Same key for Instagram profiles, posts, reels, and search when creators cross-post.
- [Creator intelligence use case](https://www.socialfetch.dev/use-cases/creator-intelligence-api): Multi-network creator cards and enrichment patterns.