All platformsLive Threads data

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 credit card requiredRead the API docs
  • No Meta app
  • Same key as Instagram
  • Failed lookups aren't charged
// Threads profile — handle goes in the path
const base = "https://api.socialfetch.dev";
const path = "/v1/threads/profiles/trendspider";

const res = await fetch(`${base}${path}`, {
  headers: { "x-api-key": "YOUR_API_KEY" },
});

const data = await res.json();
{
"handle": "trendspider",
"displayName": "TrendSpider",
"followers": 59051,
"verified": false,
"privateAccount": false,
// + 12 more — full schema in docs →
}
99.8% uptime#3 Product of the Day3,200+ developers

Teams running monitoring, research, and enrichment pipelines

We run the Threads scrapers. You build the product.

Live Threads data as JSON — proxies, platform changes and consistent output handled for you.

Threads, plus every other network

One key and one response envelope for Threads and 24 more platforms — profiles, posts, search, comments and transcripts.

Pricing you can reason about

One request, one credit. Know how far your balance will go before you run your next batch.

Live data on every request

Fetch public data when you ask for it — not from a shared cache.

No scraper maintenance

We handle proxies, browser changes, and platform breakages.

Built for production jobs

Run concurrent workloads with explicit statuses and request IDs.

Regular jobs. Better rates.

Running lookups every month? Get lower per-credit rates with a monthly plan. For occasional projects, choose pay as you go.

Never expires

What Threads data can you get?

5 endpoints, one API key. Every response comes back as live JSON in the same envelope.

Browse all 5 Threads endpoints
Use cases

What teams build with Threads data

Monitoring, enrichment, research and content workflows on Threads data — the same API as every other platform.

What you can build

Monitor brands and competitors

Find and vet creators

Check reach and engagement before you reach out.

Turn video into searchable text

Transcribe and index video and audio content so you can find the exact moment you need.

Track public communities

Follow the subreddits, groups, and channels where your audience talks.

How it works

Your first request in three steps.

Use TypeScript or your automation tool of choice.

Sources

+ 19 more platforms

One request

Social Fetch API

GET/v1/tiktok/profiles/charlidamelio

x-api-key: sk_live_••••••••

1 request · 1 credit

Same JSON shape

response.json200 OK
{
  "data": {
    "lookupStatus": "found",
    "profile": {
      "platform": "tiktok",
      "handle": "charlidamelio",
      "displayName": "charli d’amelio",
      "verified": true
    },
    "metrics": {
      "followers": 160263648
    }
  }
}
  1. Step 1

    Create your free account

    Get an API key with 100 requests included.

  2. Step 2

    Choose an endpoint

    Pass a username, URL, keyword, or post ID.

  3. Step 3

    Get clean JSON

    Use the response immediately or send it into your pipeline.

Works with your stack

Code, automate, or connect your AI.

Explore integrations

Pricing

Social data, priced simply.

Start with 100 free credits. Monthly plans give you predictable volume and lower per-request rates.

Starter

$29.00

18,000credits

  • Top up from $1.61 / 1k if you run out
  • Up to 25 monitors
Most popular

Growth

$79.00

50,000credits

  • Top up from $1.58 / 1k if you run out
  • 5 team seats
  • Up to 100 monitors

Scale

$225.00

150,000credits

  • Top up from $1.50 / 1k if you run out
  • 25 team seats
  • Up to 250 monitors
  • Cancel anytime
  • 30-day money-back guarantee
  • Price locked while you stay

Need 1M+ credits, invoicing, or volume rates? Talk to us

Trust signals

DevHunt

Product Hunt

Uneed

Customers

Teams building on Social Fetch.

“Our TikTok and Instagram scrapers broke constantly. Social Fetch took us off that rotation — we ship product again.”

Daniel Reeve · Founder, Social Crow
  • “Transcripts at volume from one endpoint. No broken scrapers for our small team to maintain.”

    Marcus Lin · Founder, Voice Gecko
  • “Live profile data on every request. We never flag accounts from a stale cache.”

    Hannah Webb · Founder, Scam Finder
  • “Heavy concurrent load, no rate limits to negotiate. The rare API I haven't wrapped in retries.”

    Owen Pritchard · Founder, IP Flare

Threads API: common questions

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.

The Threads API in detailHow the Threads routes work, what they cost, and how they differ from the official API.

Why teams use Social Fetch for Threads

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.

How to call the Threads API

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

What each Threads route returns

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

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

Pull your first Threads data.

Run a live Threads request in the playground. 100 free credits, no card, JSON back in seconds.

No credit cardSign up in 30 seconds withGoogleGitHub