Real-time Threads data, one API call.
Public Threads profiles, recent posts, and keyword search as JSON — no Meta app or Facebook Login.
The Threads API from Captapi gives developers reliable access to public Threads data without building or maintaining scrapers — send one authenticated request and get clean, structured JSON back. Public profiles, posts, and keyword search without a Meta app.
curl "https://api.captapi.com/v1/threads/profile?url=https%3A%2F%2Fwww.threads.net%2F%40zuck%2Fpost%2FC8H1abcdEFG" \
-H "Authorization: Bearer capt_live_..."What is the Threads API?
Public Threads profiles, recent posts, and keyword search as JSON — no Meta app or Facebook Login. Every endpoint is a single authenticated GET request that responds with predictable JSON, so the data drops straight into dashboards, AI pipelines, RAG systems, and no-code automations. AI agents can call the same endpoints as MCP tools via @captapi/mcp.
Compared with Threads API: Use Captapi instead of Meta's Threads API when you need public profile, post, or keyword-search JSON and you do not want to stand up a Meta app. Keep Meta's API when you must publish on a Threads account you own or read insights for that account. Threads API alternative.
Endpoints
What you can do with the Threads API
Profile
GET /v1/threads/profile
Threads profile — displayName, isPrivate, bioLinks (Meta verified), isThreadsOnlyUser, transparencyLabel, bioFragments, HD avatars (1 credit).
1 credit
User Posts
GET /v1/threads/user-posts
Recent Threads posts — engagement{views,likes,replies,reposts,quotes}, threadId/isReply. Flat 2 credits. source + timings.
2 credits
Post Details
GET /v1/threads/post-details
Threads post — engagement (views when exposed), comments[], suggestedPosts[], threadId/isReply. Flat 1 credit.
1 credit
Post Search
GET /v1/threads/search
Threads keyword search — posts with engagement + media. orderBy relevant | post_dated | engagement. Flat 2 credits.
2 credits
Search Users
GET /v1/threads/search-users
Threads user discovery from keyword search — id, handle, avatar, verified. Flat 1 credit.
1 credit
How it works
- 1. Sign up — get 100 free credits, no card required.
- 2. Create a key from your dashboard.
- 3. Call any endpoint above with
Authorization: Bearer capt_live_...and parse the JSON response. Passcache=trueto reuse a prior response from the 24h cache at no cost.
Threads API guides
Frequently asked questions
What is the Threads API?+
The Threads API is a REST API from Captapi that returns public Threads data as clean, structured JSON. It covers 5 endpoints — Profile, User Posts, Post Details, Post Search, Search Users — behind one Bearer API key, with no OAuth flow and no infrastructure to build or maintain.
What data can I get from the Threads API?+
Public Threads profiles, recent posts, and keyword search as JSON — no Meta app or Facebook Login. Each endpoint is a single GET request that responds with predictable JSON fields, so the data is ready for dashboards, AI pipelines, and automations.
Do I need a Threads developer account or OAuth?+
No. You only need a Captapi key (capt_live_...), sent as an Authorization: Bearer header. The same key works across all 33 platforms Captapi supports. We handle access, rate limits, retries, and parsing for you.
How much does the Threads API cost?+
Threads endpoints cost between 1 and 2 credits per call, depending on the endpoint and how many results you request. New accounts start with 100 free credits (no credit card). Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d.
Can AI agents use the Threads API?+
Yes. Every Threads endpoint is exposed as a tool in the official MCP server (@captapi/mcp) for Claude, Cursor, and VS Code, and is also available through the @captapi/cli CLI and the n8n-nodes-captapi community node.
Is the Threads API suitable for production use?+
Yes. It is a stable REST API with predictable JSON, automatic retries, and upstream fallbacks. Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d. Only successful responses consume credits — failed or empty results are never charged.
Do I need a Meta developer app for the Threads API?+
Not for Captapi public reads. Meta's official Threads API requires a Meta app, Facebook Login, and app review for production publish/insights. following and post counts are not on the public profile surface — we omit them rather than invent zeros. Keyword search of Meta's Top SERP is /v1/threads/search; an on-page “No results” is an empty 200 at 0 credits.
Explore other platforms
Start using the Threads API in sixty seconds
Sign up, grab your API key, and make your first request. 100 credits on the house — no credit card.