Threads API

Scrape Threads data with one API

Name: Threads Data API
Brand: SocialCrawl
Availability: InStock

Fetch public Threads data as structured JSON with one SocialCrawl API key. Same Post, Comment, and Author schema as every other platform. Reads are priced in credits.

Read the docs How it works Try live

/v1/threads

5 active endpoints

GET /v1/threads/profile
GET /v1/threads/user/posts
GET /v1/threads/post
GET /v1/threads/search
GET /v1/threads/search/users

What Threads endpoints does SocialCrawl ship?

5 live read endpoints for public Threads data. Profiles, user posts, single posts, and search. Data API only.

Profile

1 credit

/v1/threads/profile

Get Threads user profile.

handle

User posts

1 credit

/v1/threads/user/posts

List Threads user posts.

handle, trim

Post

1 credit

/v1/threads/post

Get Threads post details.

url, trim

Search

1 credit

/v1/threads/search

Search Threads posts.

query, start_date, end_date, trim

User search

1 credit

/v1/threads/search/users

Search Threads users.

query

Threads API6 endpoints supported

View docs

Returns a Threads account's public profile: bio, the external link set in that bio, follower count, profile picture URL, and verification status.

Use it when you have a handle and want the account itself; user/posts returns what that account has posted.

1 credit

GET/v1/threads/profile?handle=zuck

handle

handle · Threads username without the @ symbol

$ curl https://www.socialcrawl.dev/v1/threads/profile?handle=zuck \
    -H "x-api-key: sc_YOUR_API_KEY"

idle

// Running this live needs your own API key. Hit "Try it" to see an example response

How the Threads API works

Threads is a normal SocialCrawl social surface. You call GET /v1/threads/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second SDK.

Authenticate every call

Send your key in the x-api-key header. The same key works across the SocialCrawl catalog.

GET with query params

Routes are GET. Pass handles, urls, queries, and cursors as query strings. We validate formats before charging.

Pay in credits, not seats

Live misses debit the route tier. Cache hits cost 0. Empty or hard failures refund.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached.

The usual integration chain

Most products resolve an account, page content, then deepen only the posts that matter.

01Account

GET /v1/threads/profile

Author-shaped profile

Resolve the handle or id once.

02Feed

GET /v1/threads/user/posts

PostList of recent public items

Page with cursor or after when the route supports it.

03Item

GET /v1/threads/post

Full Post for one URL or id

List rows are not enough when you need the full record.

04Comments

GET /v1/threads/search

CommentList when the platform exposes it

Expand only when a thread matters.

request

GET /v1/threads/profile
  ?handle=zuck
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

response envelope

{
  "success": true,
  "data": { "/* Author | Post | PostList | CommentList | … */": true },
  "credits_used": 1,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align.

Authorprofile

id, username, display_name, avatar_url, bio, followers, url, ext

PostList / Postuser/posts

items[].post with id, url, content, engagement, author, published_at, ext

CommentListpost

items[] with author, content.text, engagement, published_at when comments ship

Search / Mediasearch

search hits, media metadata, or transcripts depending on route

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint.

Edge receives the call

Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency.

Validate, then debit

Registry lookup finds the route. Required params run first. Invalid input returns 400 with no charge. Valid calls debit before upstream work.

Cache or fetch

A deterministic cache key is built from platform + resource + params. Hit: credits_used = 0. Miss: upstream fetch with retries and circuit breaker.

Normalize and return

Upstream JSON is mapped to Author / Post / PostList / CommentList (or route archetype), validated, wrapped in the success envelope, and logged for billing audit.

Billing rules that matter in production

Standard live miss: tier cost (often 1 credit)
Advanced reads: typically 5 credits
Premium reads: typically 10 credits
Metered routes: min floor when documented
Cache hit: 0 credits
Empty / hard fail: auto-refund
Bad params: 400, never charged
No credits: 402, never charged
Disabled routes: 503, never charged

How we get the data

Threads is public-read data on SocialCrawl. We normalize it into the shared schema so your code does not learn a second OAuth flow.

What Threads is for this API

Public Threads surfaces exposed by the registry. Read-only for research, monitoring, and product jobs.

How SocialCrawl reaches it

Social-read upstreams behind one gateway. Prism composites combine legs when a fat route is registered.

What leaves our edge

Unified JSON envelope: success, data, credits_used, request_id, cached. Shared Author / Post / Comment leaves where archetypes align.

What we do not ship live

No write endpoints and no private inbox. Disabled routes stay out of the active count. Prefer registry docs for the live inventory.

field map sketch

public profile / channel→ author.*profile identity and counters

public post / media→ post.* / items[].postpost content and engagement

list / search page→ items[] or hitscomments or search hits when present

What this API is used for

The jobs this API is most often used for.

5active Threads endpoints in the registry

1 / 5 / 10credit ladder across standard, advanced, premium

Threads monitoring and content intelligence

Callers concentrate on profile, content lists, search, and deepen paths on Threads. Structured Threads JSON on the shared schema with one SocialCrawl API key.

Detail reads are typically a few seconds on live miss. Search and fat composites are slower paths.

What people build with the Threads API

The jobs Threads data is most often used for. Each one is a full recipe with the endpoint chain and pricing.

Social listeningKeyword search with start and end dates.

Comment scrapingKeyword search and post detail. Use it to find the discussion, then pull depth elsewhere.

Creator analyticsHandle resolution and the account's recent posts.

Influencer discoveryUser search by keyword and the handle's recent posts.

Identity resolutionHandle and post lookup, useful where a market has moved off the older networks.

Trend detectionKeyword search with start and end dates.

News and OSINT monitoringKeyword search with start and end dates, which matters in markets that have moved off the older networks.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Monitoring jobs

Python, cron, Slack bots

Poll profiles and feeds on Threads. Alert when engagement velocity jumps.

Research and VoC

Node, notebooks, BI loads

Search and expand posts for brand, product, and competitor language on Threads.

Backend product jobs

Go, workers, Explorer

Wire resolve to list to detail into pipelines. Cache hits keep recurring runs cheap.

Call it in two lines

Live misses spend credits by tier. Cache hits are free. Empty or hard failures refund.

curl "https://www.socialcrawl.dev/v1/threads/profile?handle=zuck" \
  -H "x-api-key: sc_your_api_key_here"

curl "https://www.socialcrawl.dev/v1/threads/user/posts?handle=zuck" \
  -H "x-api-key: sc_your_api_key_here"

Threads on SocialCrawl

Same key as the rest of the catalog

Platform docs Get an API key

Endpoints

What data does the Threads API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

ProfileGet Threads user profile User PostsList Threads user posts PostGet Threads post details SearchSearch Threads posts Post CommentsGet comments on a Threads post Search UsersSearch Threads users

Comparison

How does SocialCrawl compare to Threads API (Meta) for Threads data?

Same Threads data, two very different paths. Auth, rate limits, schema, and cost, side by side.

Feature	SocialCrawl	Threads API (Meta)
Authentication	One x-api-key header	OAuth with Meta developer app credentials
Setup / approval	Sign up and call immediately	Meta app creation, review, and permission approval
Rate limits	Credit-based, pay per request	Per-user and per-app quotas enforced by Meta
Response schema	Unified JSON shared across 51 platforms	Graph-API-style fields specific to Threads
Pricing	1 credit per request; 100 free credits on signup	Free, but limited to data your authorized users grant
Data coverage	Any public profile, post, keyword search, or user search	Mostly your own account's data; official posting and insights
Maintenance	Schema stays stable when Threads changes internals	You track Meta API versioning and permission changes

Authentication

SocialCrawl

One x-api-key header

Threads API (Meta)

OAuth with Meta developer app credentials

Setup / approval

SocialCrawl

Threads API (Meta)

Meta app creation, review, and permission approval

Rate limits

SocialCrawl

Credit-based, pay per request

Threads API (Meta)

Per-user and per-app quotas enforced by Meta

Response schema

SocialCrawl

Unified JSON shared across 51 platforms

Threads API (Meta)

Graph-API-style fields specific to Threads

Pricing

SocialCrawl

1 credit per request; 100 free credits on signup

Threads API (Meta)

Free, but limited to data your authorized users grant

Data coverage

SocialCrawl

Any public profile, post, keyword search, or user search

Threads API (Meta)

Mostly your own account's data; official posting and insights

Maintenance

SocialCrawl

Schema stays stable when Threads changes internals

Threads API (Meta)

You track Meta API versioning and permission changes

FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

How do I scrape Meta Threads data with an API?

SocialCrawl provides 6 Threads API endpoints covering profiles, user posts, post details, keyword search, and user search. Send a GET request with x-api-key. No OAuth, no Meta app review, no business account required.

What Threads endpoints does SocialCrawl offer?

6 endpoints: Profile, User Posts, Post, Search, Post Comments, and Search Users. Every response uses the same unified schema.

How much does the Threads API cost?

All 6 Threads endpoints cost 1 credit per request on the standard tier. New accounts get 100 free credits with no credit card required, enough to make 100 Threads calls before you pay a cent.

Do I need OAuth or a Meta developer account?

No. Unlike the official Threads API, SocialCrawl does not require OAuth, app review, or a business Threads account. Pass the handle or URL and your SocialCrawl x-api-key. The response comes back as ready-to-use JSON.

Is it legal to scrape Threads with this API?

SocialCrawl accesses only publicly visible Threads data through our upstream provider. You are responsible for complying with Meta's terms of service and applicable data protection regulations in your specific use case. SocialCrawl operates under a documented GDPR legitimate-interest framework: public, logged-out data only, no credential use, short-lived caches (2 to 30 minutes) with no persistent store, and a public opt-out channel for anyone whose public info appears in responses. Full details: socialcrawl.dev/legal/public-data-notice.

Can I search Threads posts by keyword?

Yes. The search endpoint takes a query string plus optional start_date and end_date filters, returning matching posts with text, like counts, author info, and timestamps. Perfect for social listening and brand monitoring.

What is the best Threads scraper API?

SocialCrawl offers the most direct route to public Threads data: 6 endpoints for profiles, user posts, post details, keyword search, and user discovery, each costing 1 credit. New accounts get 100 free credits with no credit card, and there is no Meta developer app, OAuth flow, or business account requirement.

Does Threads have a data API?

Yes, with a caveat worth knowing. Meta ships an official Threads API, but it is scoped to publishing and reading your own account, not arbitrary public profiles. For a Threads data API that reads any public profile, post, or keyword search, SocialCrawl covers profiles, user posts, post details, keyword search, and user discovery in one unified schema, at 1 credit per call with 100 free credits on signup and no Meta app review.

Threads scraping API vs the official Threads API: what's the difference?

With SocialCrawl there is no app review or approval queue. Sign up and call Threads endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.

Ask AI about SocialCrawl

Ask ChatGPT Ask Perplexity Ask Gemini Ask Claude Ask Grok

Related APIs and tools

Adjacent endpoints and free tools on SocialCrawl. The tools run without an API key.

instagram scraper api

Read the Threads API reference in the docs

🤖 AI agent or LLM? Read this page as markdown