Best Threads API in 2026: Pricing Compared
Best Threads API in 2026 by listed price: 9 SandBase endpoints, eight at $0.002 and Profile Search at $0.003. Official Threads rate limits have no dollar table.

Official Threads usage is an impression formula, not a dollar menu. On the 21 Nov 2026 catalog check (Asia/Shanghai), Threads on SandBase listed 9 endpoints. Eight were $0.002 per call. Profile Search was $0.003. The Threads overview redirects to the documentation overview. It describes a product that enables people to create and publish content on a person’s behalf. Calls within 24 hours equal 4800 times the number of impressions, with a minimum of 10 impressions. Separate 24-hour caps are 250 API-published posts, 1,000 replies, 100 deletions, and 500 location searches. There is no dollar price table. Official per-call prices stay Unknown. Accuracy and latency stay Unknown. This is not a third-party bake-off.
Key takeaway
- On 21 Nov 2026 the SandBase Threads hub listed 9 endpoints. Eight were a flat $0.002 per call.
threads/web/search-profileswas $0.003. Do not flatten the hub to $0.002. One thousand calls at $0.002 are $2.00 as list-price math, not a bill.- User Profile (
web/user-info), Recent Search (web/search-recent), and User Posts (web/user-posts) showed “100 free calls / day — First 100 calls per day free (shared per organization) · Resets at 00:00 UTC. Pay per call after that.” That pool is 100 calls per organization per UTC day, shared, not 100 per card. Profile Search did not show the row. The hub is not a free-quota badge. Do not mark post detail, user replies, or user reposts eligible.- Official Threads publishes rate limits and no per-call dollar table. Official per-call $ is Unknown.
- Call
POST https://api.sandbase.ai/v1/api/threads/web/{endpoint}with a Bearer key and JSON. The Threads cards in this comparison were not flagged asynchronous. Do not POST/v1/runto start.
What a Threads API means in 2026
Three products share the name. The impression math prices none of the research cards below.
The first is Meta’s Threads API for acting on a person’s behalf: create and publish, inside the rolling impression budget and the 24-hour caps on posts, replies, deletions, and location searches. The overview page returned a usable body and an empty HTML title, so this article does not quote a title string and does not screenshot that page. Official per-call dollars were not on it.
The second is a separate unofficial vendor account. This article does not name those vendors or borrow accuracy scores.
The third is the SandBase hub. The HTML title was “Threads APIs: Research Public Posts and Conversation Context | SandBase.” The blurb covers user profiles, user posts, replies and reposts, post details, post comments, and recent, top, and profile search. The Markdown twin counted 9 endpoints. SandBase is not Threads. Official Threads terms still apply.
Publishing for an authorized account stays on the official overview. A public profile, a recent keyword search, or a post list with a listed per-call price is a card on the hub. The impression formula is a ceiling on official calls, not an invoice you subtract from $0.002.
Threads API endpoints you can call on SandBase today
Do not flatten the hub to $0.002. Profile Search is $0.003. The wider data API index listed 2,247 endpoints from 182 providers on the same check. The Social Media category footer counted 1,235 APIs. Those censuses can change.
| Card | List price, 21 Nov 2026 | Call | What the card describes | Async | Free allowance |
|---|---|---|---|---|---|
| User Profile | $0.002 per call | POST /v1/api/threads/web/user-info | Bios, followers, verification | Not flagged | Visible 100/day row |
| Recent Search | $0.002 per call | POST /v1/api/threads/web/search-recent | Keyword-matched new posts | Not flagged | Visible 100/day row |
| User Posts | $0.002 per call | POST /v1/api/threads/web/user-posts | Account updates with cursors | Not flagged | Visible 100/day row |
| Profile Search | $0.003 per call | POST /v1/api/threads/web/search-profiles | Accounts by text query | Not flagged | No visible row |
Also on the hub at $0.002, and not marked eligible here: web/post-detail, web/post-detail-v2, web/user-replies, web/user-reposts, and web/user-info-by-id. That is the rest of the eight $0.002 paths. This check did not open those five as screenshot cards. A pricing-page sample names threads/web/search-recent and threads/web/post-detail-v2. The sample is not a complete roster, and a sample line is not the visible row. Profile Search is the $0.003 card. A README sentence about a daily quota is not the row. The row was absent on that card.

SandBase Threads hub, logged out, light theme, 21 Nov 2026 (Asia/Shanghai). HTML title: “Threads APIs: Research Public Posts and Conversation Context | SandBase.” The page is the 9-endpoint catalog. It is not a free-quota badge.

SandBase Threads User Profile card, logged out, light theme, 21 Nov 2026 (Asia/Shanghai). HTML title: “Threads User Profile API: Bios, Followers and Verification | SandBase.” The Markdown price was $0.002 per call. The card showed the shared 100-free-calls row.

SandBase Threads Recent Search card, logged out, light theme, 21 Nov 2026 (Asia/Shanghai). HTML title: “Threads Recent Search API: Get Keyword-Matched New Posts | SandBase.” The Markdown price was $0.002 per call. The card showed the shared 100-free-calls row.

SandBase Threads User Posts card, logged out, light theme, 21 Nov 2026 (Asia/Shanghai). HTML title: “Threads User Posts API: Browse Account Updates with Cursors | SandBase.” The Markdown price was $0.002 per call. The card showed the same shared 100-free-calls row.

SandBase Threads Profile Search card, logged out, light theme, 21 Nov 2026 (Asia/Shanghai). HTML title: “Threads Profile Search API: Find Accounts with Text Queries | SandBase.” The Markdown price was $0.003 per call. The card did not show a 100-free-calls row and is not free-quota eligible.
Official Threads API pricing versus the SandBase catalog
The rows are different products. Latency and accuracy are Unknown in every row.
| Path | What you can call, as checked 21 Nov 2026 | Billing | Free trial or allowance | Docs |
|---|---|---|---|---|
| Official Threads API | Create and publish content on a person’s behalf. The overview states the impression formula and the 24-hour caps on posts, replies, deletions, and location searches. | No dollar price table. Official per-call $ Unknown. Rate limits are not a SandBase price. | The impression budget and the 24-hour caps. That is not the SandBase daily allowance. | Threads overview |
| SandBase Threads hub | 9 research endpoints. Eight at $0.002. Profile Search at $0.003. | Pay per call, no subscription. Start ($0), Build (Metered), Scale (Custom). | User Profile, Recent Search, and User Posts showed the shared 100-calls row. Profile Search did not. Post detail, user replies, and user reposts are not marked eligible. | Live cards plus API passthrough |
| A separate unofficial vendor account | Whatever that vendor lists. Not measured here. | That vendor’s contract. Unknown here. | Unknown here. | That vendor’s own docs |
Same catalog, separate hubs, not a bake-off: Instagram (107, $0.001), Facebook (28, From $0.0011), and Twitter (47, From $0.0001). The Twitter hub title is “Twitter/X APIs: Search Posts and Public Account Activity | SandBase.” /apis/x returned HTTP 404. Do not link it. Pricing posts for those hubs: Best Instagram API in 2026, Best Facebook API in 2026, and Best Twitter API in 2026.
Best Threads API for each need
- Lowest listed price: the eight cards at $0.002, including User Profile, Recent Search, and User Posts. One thousand of those calls are $2.00 only if every call bills at $0.002.
- Account search at the higher list price: Profile Search at $0.003. One thousand of those calls are $3.00 on the same assumption. The card is not free-quota eligible.
- Confirmed free-quota cards in this check: User Profile, Recent Search, and User Posts only. They share one organization pool. They do not each grant 100 calls.
- Publishing on a person’s behalf, inside Meta’s rate limits: the official Threads overview, not this hub.
- A public post archive on X lives on the Twitter hub above.
/apis/xis not that hub.
How to call the Threads API on SandBase
Data APIs use POST https://api.sandbase.ai/v1/api/{vendor}/{endpoint} with Authorization: Bearer $SANDBASE_API_KEY and a JSON body. The hub page is the catalog. The call is the POST. Language models use POST /v1/chat/completions. Media models use POST /v1/run. Do not start a data API with POST /v1/run. The passthrough reference is the data-API page.
User Profile, Recent Search, User Posts, and Profile Search were not flagged asynchronous on 21 Nov 2026. If a live card later says the endpoint runs asynchronously, poll GET https://api.sandbase.ai/v1/run/{id} until status is completed. That GET is the poll. Do not POST /v1/run to start. This comparison did not run a paid call. Replace the empty object with the fields on the live card. Read outputs[0].data. If that object is missing, fail loudly.
import os
import requests
payload = {} # replace with the fields on the live Recent Search card before sending
headers = {
"Authorization": f"Bearer {os.environ['SANDBASE_API_KEY']}",
"Content-Type": "application/json",
}
response = requests.post(
"https://api.sandbase.ai/v1/api/threads/web/search-recent",
headers=headers,
json=payload,
timeout=90,
)
response.raise_for_status()
body = response.json()
# Recent Search was not flagged asynchronous on 21 Nov 2026.
# Do not POST /v1/run to start the data API.
outputs = body.get("outputs") or []
if body.get("status") not in (None, "completed") or not outputs or not isinstance(outputs[0], dict):
raise RuntimeError(f"SandBase call did not complete: {body.get('status')} {body.get('error')}")
data = outputs[0].get("data")User Profile is /v1/api/threads/web/user-info. User Posts is /v1/api/threads/web/user-posts. Profile Search is /v1/api/threads/web/search-profiles. The snippet is a client sketch, not a measured latency.

SandBase API passthrough page, logged out, light theme, 21 Nov 2026 (Asia/Shanghai). HTML title: “API Passthrough.” It documents POST /v1/api/{vendor}/{endpoint} for data APIs. It is not a Threads price.
What the Threads API daily allowance covers
Pricing and Pricing and Usage, checked 21 Nov 2026, give every organization 100 free data API calls per UTC day for eligible tools. The pool is shared across eligible data APIs and all org keys, resets at 00:00 UTC, and does not carry over. It is not 100 calls per card. It is not “every data API is free for the first 100 calls.” Some data APIs are billed from the first call. The billing page names some batch endpoints, crawl endpoints, Xiaohongshu PGY, and Douyin Xingtu kol-* routes as examples. This article marks a Threads card eligible only when the live card showed the row. User Profile, Recent Search, and User Posts did. Profile Search did not. Post detail, user replies, and user reposts are not marked eligible. After the 100th eligible call, requests still complete and are billed at the listed price. A zero balance can still spend remaining allowance. Failed calls are not charged. Catalog browsing is $0. Plans are Start ($0), Build (Metered), and Scale (Custom). Language models and media models are not in the pool.

SandBase pricing page, logged out, light theme, 21 Nov 2026 (Asia/Shanghai). HTML title: “SandBase Pricing: Models, APIs and Usage-Based Billing.” Plans are pay per call. The page is not a Threads rate card.

SandBase Pricing and Usage guide, logged out, light theme, 21 Nov 2026 (Asia/Shanghai). HTML title: “Pricing and Usage.” Eligible data APIs share 100 free calls per organization per UTC day. Only the Threads cards that showed the row are described as eligible.
One thousand User Profile calls at $0.002 are $2.00 if every call bills at the list price. One thousand Profile Search calls at $0.003 are $3.00 on the same assumption. That is list-price math, not an invoice. Subtract the shared 100 only for calls that actually drew on a card showing the row, and only until the organization pool is gone. Do not subtract 100 from Profile Search. Do not subtract 100 three times because three cards showed the row.
When the cards look right, open Console API keys, read pricing, and use signup, which currently redirects to sign-in. Agents can start from the SandBase skill file.
When not to use the SandBase Threads API
Stay on the official Threads overview to create and publish on a person’s behalf, inside the impression budget and the 24-hour caps. Official Threads terms still apply. Stay put when you need a measured accuracy or latency rank. This check did not produce one.
Threads API FAQ
What does “Threads API” mean in this article?
The 9 SandBase cards on /apis/threads, checked 21 Nov 2026. The official product that publishes on a person’s behalf stays on the Threads overview and is a different product.
When is the SandBase hub a better fit than the official Threads API?
For a public profile, a recent keyword search, a user’s posts, or a profile text search, billed per call on one key. For publishing on a person’s behalf, start with the official overview. Official per-call dollars stay Unknown.
How much do the SandBase Threads API endpoints cost?
$0.002 per call on eight cards, and $0.003 on Profile Search, on the 21 Nov 2026 hub. One thousand calls at $0.002 are $2.00 as list-price math.
Are the first 100 Threads API calls free?
User Profile, Recent Search, and User Posts showed the shared row: 100 free calls per organization per UTC day, resetting at 00:00 UTC, then the listed price. Profile Search did not. Post detail, user replies, and user reposts are not marked eligible. The allowance is shared, not 100 per card.
How do official Threads API limits compare with SandBase?
Official calls within 24 hours equal 4800 times impressions, with a minimum of 10 impressions, plus 250 API-published posts, 1,000 replies, 100 deletions, and 500 location searches. SandBase lists 9 research endpoints with public per-call prices. Latency and accuracy were not measured. The impression formula is not a dollar invoice.
Do official Threads terms still apply?
Yes. A catalog price is not a license to ignore them.
How do I start a Threads API call?
POST https://api.sandbase.ai/v1/api/threads/web/search-recent (or web/user-info, web/user-posts, web/search-profiles) with a Bearer key. Do not POST /v1/run to start. Poll GET https://api.sandbase.ai/v1/run/{id} only if that live card says the endpoint is asynchronous. These cards were not flagged asynchronous.
Where is the Twitter or X hub?
Use Twitter on SandBase, 47 endpoints. /apis/x returned HTTP 404. It is not a hub.
Related Threads API reading
Field notes, not rewritten here: Threads Public Data API and Threads Creator Research API. Neighboring price posts: Best Instagram API in 2026, Best Facebook API in 2026, and Best Twitter API in 2026. The wider map is Best Social Media Data APIs for AI Agents (2026).
Open the Threads hub, then User Profile or Recent Search beside the passthrough reference. Create a key in the Console, read pricing, or start from the skill file.
Found this useful? Share it