Best Twitter API in 2026: X API Pricing Compared
Best Twitter API in 2026: 47 SandBase endpoints from $0.0001 per call, beside official X API per-resource credits. The two price units are not equivalent.

Searchers still type “Twitter API.” The official product is the X API, and it bills in a different unit from the catalog most people compare it with. On the 21 Nov 2026 check (Asia/Shanghai), Twitter on SandBase listed 47 endpoints, from From $0.0001 per call on Community and Trends to $0.014286. Official X API v2 is pay-per-usage on credits: reads are priced per resource, writes per request. Posts: Read was $0.005 per resource and User: Read was $0.010 per resource on the official pricing page. Those figures are not SandBase per-call prices, and this article does not convert one into the other. Accuracy and latency against other vendors stay Unknown.
Key takeaway
- The live hub is
/apis/twitter(47 endpoints)./apis/xreturned HTTP 404 on 21 Nov 2026. Do not use that path.- Cheapest listed SandBase floors: Community and Trends, each From $0.0001 per call. The hub spans up to $0.014286. Seventeen cards were “From” floors and 30 were flat.
- Search timeline and User profile are each $0.001 per call and confirmed eligible for the shared daily allowance. Community and Trends were not.
- Official X billing is credit-based, with no subscriptions. Pay-per-usage plans are capped at 3 million Post reads per monthly billing cycle. Higher volume is described as Enterprise.
- Call
POST https://api.sandbase.ai/v1/api/twitter/{endpoint}with a Bearer key. Do not start a data API withPOST /v1/run.
What a Twitter API and the X API mean in 2026
Three products share the name.
The official path is the X API. About the X API (title “About the X API - X”) says v2 uses pay-per-usage pricing, credit-based, with no subscriptions, and that the same resource requested twice in 24 hours is charged once. X API pay-per-usage pricing and credits (title “X API pay-per-usage pricing and credits - X”) is the rate card fetched on 21 Nov 2026. Reads are charged per resource returned. Confirmed examples: Posts: Read $0.005 per resource; User: Read $0.010 per resource; Like, Mute, and Block Read $0.001; List, Space, Community, and Note Read $0.005; Following, Followers, and DM Event Read $0.010. Write examples include Post: Create at $0.015 per request and Post: Create (with URL) at $0.200 per request. Pay-per-usage plans are capped at 3 million Post reads per monthly billing cycle. The page says higher volume means an Enterprise plan. It also says new payers can earn $20 in free X API credits after saving a first eligible payment card and completing a first credit purchase, plus a match of the first auto-recharge up to $50, and up to 20% back in free xAI API credits. Prices are subject to change. Current rates are on that page and in the Developer Console. developer.x.com/en returned 404. A Developer Console URL redirected to an X login wall, so this article does not describe that screen.
The second product is a separate unofficial vendor account. This article does not name those vendors or borrow their scores.
The third is the SandBase hub. The HTML title was “Twitter/X APIs: Search Posts and Public Account Activity.” The H1 was “Twitter.” The Markdown twin said “Twitter API on SandBase,” 47 endpoints, covering public X/Twitter surfaces for social monitoring and audience research: tweet search, profile timelines, followers, following, lists, and rich profile metadata. SandBase is not X. Official X terms still apply.
The unit is the decision. A $0.005 official Post read and a $0.001 SandBase search call are different meters. Quoting either number as the other’s price would invent an equivalence this check did not establish.
Twitter and X API endpoints on SandBase today
The data API index listed 2,247 ready-to-call data API endpoints from 182 providers. llms.txt listed 2,807 models and APIs. The Social Media footer count was 1,235 APIs. The category page is Social Media APIs. Do not flatten 47 cards to the $0.0001 floor.
| Card | List price, 21 Nov 2026 | Call | Notes | Async | Free allowance |
|---|---|---|---|---|---|
| Community | From $0.0001 per call | POST /v1/api/twitter/community | Community details by URL. Cheapest listed floor, tied with Trends | Not flagged | Unknown |
| Trends | From $0.0001 per call | POST /v1/api/twitter/trends | Trends card. HTML title on the live page is awkward; this article does not rewrite it | Not flagged | Unknown |
| Search timeline | $0.001 per call | POST /v1/api/twitter/web/search-timeline | Posts, authors, engagement counts. Also on the pricing-page sample list | Not flagged | Confirmed |
| User profile | $0.001 per call | POST /v1/api/twitter/web/user-profile | Bios, counts, account creation. Also on the pricing-page sample list | Not flagged | Confirmed |
“From” is a floor. The hub’s high listed price that day was $0.014286. This article does not describe a ceiling above a floor, and it does not dump all 47 names.

SandBase Twitter hub, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “Twitter/X APIs: Search Posts and Public Account Activity | SandBase.” The page is the 47-endpoint catalog. The path is /apis/twitter.

SandBase Twitter Search card, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “Twitter Search API: Find Posts, Authors and Engagement Counts | SandBase.” The Markdown price was $0.001 per call, and the Facts block confirmed the daily free allowance.

SandBase X User Profile card, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “X User Profile API: Inspect Bios, Counts and Account Creation | SandBase.” The Markdown price was $0.001 per call, with a Facts free-allowance line.

SandBase Trends card, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The live HTML title is “X (Twitter) X / Twitter Trends API: Pricing & Specs | SandBase.” The Markdown price was From $0.0001 per call. Free-allowance eligibility on this card is Unknown.
Official X API pricing versus SandBase per-call prices
The rows are different products and different units. 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 X API | v2 pay-per-usage. Reads per resource, writes per request. Examples: Posts: Read $0.005 per resource; User: Read $0.010 per resource. Cap of 3 million Post reads per monthly cycle on pay-per-usage. | Credits in the Developer Console. No subscriptions. Prices subject to change. | $20 credit incentive on a first eligible card and first purchase, plus an auto-recharge match up to $50, and up to 20% back in xAI API credits. Dedup: the same resource twice in 24 hours is charged once. | Pricing and credits |
| SandBase Twitter hub | 47 research endpoints. Community and Trends From $0.0001. Search timeline and User profile $0.001 flat. High listed price $0.014286. | Pay per call, no subscription. Start ($0), Build (Metered), Scale (Custom). | Search timeline and User profile are confirmed eligible. The shared pool is 100 eligible data API calls per organization per UTC day, not 100 calls reserved for Twitter. Community and Trends are Unknown. | 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 social hubs, each priced on its own page: LinkedIn (38), Reddit (35), YouTube (54), TikTok (175), Facebook (28), and Instagram (107).
Best Twitter API for each need
- Lowest listed SandBase floor: Community or Trends, From $0.0001. Treat that as a minimum.
- A flat search card with a confirmed free-allowance line: Search timeline, $0.001. User profile is the matching flat profile card, also $0.001 and confirmed eligible.
- Official posting, official authenticated reads, or volume above the 3 million Post-read pay-per-usage cap: the X developer docs and, for higher volume, the Enterprise path they describe. Official support stays there.
- One key that also opens the other social hubs: the SandBase catalog. Read each hub’s own price. Comparisons: Best LinkedIn API in 2026, Best Reddit API in 2026, Best YouTube API in 2026, Best TikTok API in 2026, Best Facebook API in 2026, and Best Instagram API in 2026.
How to call the Twitter 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. 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. The first API call walkthrough is chat completions only.
Search timeline and User profile were not flagged asynchronous. If a live card says the call is asynchronous, poll GET https://api.sandbase.ai/v1/run/{id} until status is completed. That GET is the poll. The path includes the slash in twitter/web/search-timeline. This comparison did not run a paid call. Replace the empty object with the fields on the live card. Read outputs[0].data.
import os
import requests
payload = {} # replace with the fields on the live Search timeline 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/twitter/web/search-timeline",
headers=headers,
json=payload,
timeout=90,
)
response.raise_for_status()
body = response.json()
# Search timeline was not flagged asynchronous on 21 Nov 2026.
# If the live card says async, poll GET /v1/run/{id}. Do not POST /v1/run to start.
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/twitter/web/user-profile. Trends is /v1/api/twitter/trends. Community is /v1/api/twitter/community. The snippet is a client sketch, not a measured latency.

SandBase API passthrough page, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “API Passthrough.” Data APIs submit with POST /v1/api/{vendor}/{endpoint}. This page is not an X API credit balance.
What the daily allowance covers on these Twitter cards
Pricing and Pricing and Usage, checked 21 Nov 2026, give every organization 100 free data API calls per UTC day for eligible tools, shared across those tools and all org keys, resetting at 00:00 UTC with no carry-over. Language models, media models, and some pricier or formula-priced data APIs are billed from the first call. The billing page’s examples include some batch endpoints, crawl endpoints, Xiaohongshu PGY, and Douyin Xingtu kol-* routes. A card is confirmed here only with a Facts free-allowance line. Search timeline and User profile have that line and also appear on the pricing-page sample. Community and Trends do not. After the 100th eligible call, later calls still complete and are billed. 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). The sample list is not a complete roster, and two eligible Twitter cards do not make the other 45 eligible.

SandBase pricing page, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “SandBase Pricing: Models, APIs and Usage-Based Billing.” Pay per call, no subscription. This is not the X API credit rate card.

SandBase Pricing and Usage guide, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “Pricing and Usage.” The 100 calls are shared by eligible data APIs. Only Search timeline and User profile are confirmed eligible on this hub.
One thousand Search timeline calls at $0.001 are $1.00 if every call is billed. If the free allowance applies, the organization’s shared 100 eligible calls that UTC day are not charged, and that pool is shared with every other eligible data API, so this article does not reserve 100 calls for Twitter. One thousand Trends calls at the $0.0001 floor are $0.10 only if every call bills at the floor and none of the allowance applies. Trends eligibility is Unknown. That is list-price math, not an invoice. Open pricing and signup. Signup currently redirects to sign-in.
When not to use the SandBase Twitter hub
Stay on the X API when you need official posting, official authenticated user reads, the official credit console, or volume the pay-per-usage cap sends to Enterprise. Stay there when you need official per-resource billing rather than a catalog per-call price. Official X terms still apply either way. Stay put when the buying criterion is a measured accuracy or latency rank among unofficial providers. This check did not produce that rank.
FAQ
Is the Twitter API the same product as the X API?
The official product documented at docs.x.com is the X API. The SandBase hub is titled Twitter and lives at /apis/twitter. /apis/x was HTTP 404 on 21 Nov 2026.
Which SandBase card is the cheapest?
Community and Trends, each From $0.0001 per call. That is a floor. Search timeline and User profile are flat $0.001 and are the cards with a confirmed free-allowance line.
Are the first 100 Twitter calls free?
Only as a statement about eligible cards. Search timeline and User profile are confirmed eligible. They share the organization’s 100 eligible data API calls per UTC day with every other eligible tool. Community, Trends, and the rest of the hub stay Unknown until their own cards say otherwise.
How do official X prices compare with SandBase?
Official reads are per resource on a credit balance. SandBase lists per call. Posts: Read at $0.005 per resource is not a translation of Search timeline at $0.001 per call. This article does not invent an equivalent.
Do official X terms still apply?
Yes. A catalog price is not a waiver of X’s terms.
How do I start a call?
POST https://api.sandbase.ai/v1/api/twitter/web/search-timeline or /v1/api/twitter/web/user-profile 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.
Related reading
Walkthroughs, not rewritten here: X/Twitter Public Data API, Twitter Keyword Search API, X/Twitter Post Snapshot API, and X/Twitter API for AI Agents. The wider map is Best Social Media Data APIs for AI Agents (2026).
Open the Twitter hub, then Search timeline or User profile beside the passthrough reference. Read pricing and Pricing and Usage, then sign up.
The Threads pricing post on the same catalog is Best Threads API in 2026. The live Twitter hub remains /apis/twitter.
Found this useful? Share it