Skip to content

The cheapest pay-as-you-go
Twitter / X API.

Every endpoint $0.0008 per call. Returns ~20 tweets per call, just $0.04 per 1,000 tweets. No subscriptions, no developer account needed.

$0.0008

per call, every endpoint.

STANDARD
$0.04/1K

tweets, 20 per call.

VALUE
$0.50

free credits at signup.

NO CARD
51

endpoints: 37 reads, 14 writes.

COVERAGE

TwitterAPIs is a pay-per-call Twitter and X API. Each read call costs $0.0008 and returns about 20 tweets ($0.04 per 1,000). There are no subscriptions, no monthly minimums, and no X developer account required. New accounts get $0.50 in free credits, roughly 625 API calls, with no credit card.

We priced every read call at a flat $0.0008 (source: our published pricing), about 20 tweets each, so 1,000 tweets cost $0.04, versus the $5 to $10 the official X API charges for the same reads.

Endpoints

51 endpoints.
One bearer token. No developer account.

37 read endpoints and 14 write endpoints covering tweets, users, threads, timelines, and follower graphs. All at $0.0008 per call with JSON responses and standard HTTP auth.

  ┌──────────┐
  │ query_   │
  ├──────────┤
  │ ░░░░░░░░ │
  └──────────┘

Advanced Tweet Search

Search by keyword, hashtag, user mention, date range, and more. The same advanced operators you use on X.com.

    ◉
  ┌─────┐
  │░░░░░│
  └─────┘

User Profiles

Fetch full user info: bio, follower count, following, tweet count, and verified status by handle or ID.

  ┌─┐
  │ │►──
  └┬┘
   │►──
  ┌▼┐
  │ │
  └─┘

Thread Lookup

Expand any tweet into a full conversation thread. Great for AI summarisation, research, and content analysis.

  │▄ █ ▄ █
  │█ █ █ █
  │█ █ █ █
  └────────

Timeline Access

Retrieve any user's recent tweets and replies. Paginate through history without hitting X's rate limits.

  ◉─◉─◉
  │ │ │
  └─┼─┘
    ◉
    │

Follower Graph

List followers and following for any public account. Build social graphs, find influencers, map communities.

  [AI]
  ──►
  API
  ──►
  [you]

MCP Server

Plug twitterapis.com into Claude, Cursor, or any MCP-compatible AI agent. Fetch Twitter data from your prompts.

Quickstart

Three steps to
your first tweet.

terminal
1# Sign up at twitterapis.com/signup
2# Then grab your key from Settings
3
4export TWITTERAPIS_KEY="twitterapis-your_api_key_here"
5
6echo $TWITTERAPIS_KEY
Ready

Reliability

No rate limits.
No caps. Just data.

A managed API that returns clean, structured Twitter data on demand. No official X developer app, no API tiers, no quota resets. You only pay for the calls you make.

No platform rate limits

twitterapis.com imposes zero platform-level rate limits. Call any endpoint as often as your credits allow.

🔄

Automatic failover

Built-in redundancy and automatic retries keep your data flowing, even under heavy load.

🌐

No X developer account

Skip the official X developer application, approval queue, and app credentials. Sign up and call the API in minutes.

99.9%
Uptime
51
Endpoints (37 reads + 14 writes)
JSON
Structured responses
0
Rate limits imposed
// Service status
Uptime: 99.9% target
Failover: automatic
Auth: bearer token
No X developer account required

Pricing

The numbers speak
for themselves.

All systems operational
$0.0000
per call
every endpoint, standard
$0.00/1K
per 1,000 tweets
~20 tweets per call
$0.00
free credits
no credit card needed
0+
API endpoints
tweets, users, threads, search
Live API activity
nowGET /twitter/tweet/advanced_searchus-east-120041ms
1sGET /twitter/user/infoeu-west-120029ms
2sGET /twitter/user/followersap-south-120067ms
3sGET /twitter/tweet/threadus-west-220038ms

Build with

Works with your stack.
Instantly.

Standard REST + JSON means twitterapis.com slots into any language or framework. Plus a first-party MCP server and Postman collection so you can start in seconds.

  >>>
  ...

Python

Language

  [JS]
  ---

Node.js

Language

  curl
  ────

cURL

CLI

  [AI]
  ───

Claude MCP

AI Agent

  { }
  ───

Cursor

AI IDE

  GET
  ──►

Postman

API Client

  📄
  ───

Fern Docs

Interactive Docs

Wire it into your agent over plain REST.

Every endpoint is one HTTP GET with a Bearer key, so your AI can fetch tweets, users, and threads directly from your prompts today. A native MCP server for Claude and Cursor is on the way.

View Docs
// One call, Bearer auth
curl https://api.twitterapis.com/twitter/tweet/advanced_search
-H "Authorization: Bearer $TWITTERAPIS_KEY"
// MCP server for Claude & Cursor
// live: npx -y @twitterapis/mcp@latest

Privacy

Your credentials stay yours.

No stored passwords. Reads stay on public data with no login; write actions never persist your credentials. We keep it simple so you can trust it.

  ╔═══╗
  ║ ✕ ║
  ╚═══╝

No X credentials stored

We never ask for or store your Twitter/X login or password. Only your twitterapis.com API key is used.

  ┌───┐
  │ -> │
  └───┘

Most reads need no login

Most of the 37 read endpoints touch only public data with no credentials. Private reads and write actions use an X session you register, stored encrypted at rest with AES-256-GCM until you replace it, or one you pass per request, which is never stored.

  ╭───╮
  │ 🔒│
  ╰───╯

HTTPS encryption

All API traffic travels over TLS 1.3. Your API key is transmitted only in encrypted request headers.

  [===]
  [tok]

Bearer token auth

Simple revocable bearer tokens. Lost or leaked? Generate a new key from your dashboard instantly.

  ◉─◉
  │pub│

Public data only

twitterapis.com only accesses publicly visible tweets and profiles. Private accounts are never accessible.

  ▪ ✕ ▪
  ─────

No data resale

We store only your email and API usage logs. We never sell, share, or train models on your request data.

🔒

What we store

We store your email address, hashed password (if applicable), and per-call usage logs for billing. That is all. No tweet content, no X credentials, no browsing data. Read our Privacy Policy →

For developers

Integrate in under
5 minutes.

One endpoint, one header. Fetch tweets, users, and threads from any language. No OAuth dance, no rate-limit math, no developer account required.

No X developer account

Use twitterapis.com without managing official X developer app credentials or waiting for approval.

Per-call pricing

Pay only for what you use. No monthly minimums. $0.50 free credits to start, no card required.

Standard REST / JSON

Plain HTTP GET requests, JSON responses. Works with any language, framework, or AI agent.

SDK + Postman + MCP

Python package, npm package, Postman collection, Fern docs, and an MCP server for AI agents.

1export KEY="ta_your_api_key_here"
2
3curl -s \
4 -H "Authorization: Bearer $KEY" \
5 "https://api.twitterapis.com/twitter/tweet/advanced_search?query=openai%20filter:verified&limit=20" \
6 | jq '.tweets[].text'
$pip install twitterapis-python
MCP server: npx -y @twitterapis/mcp@latest

Frequently asked questions

What the API returns, what it costs, and what we do with your data.

TwitterAPIs gives you programmatic access to public X data: individual tweets, reply chains, full threads, user profiles, follower and following lists, and keyword search. Every supported route and its per-call price is listed on the TwitterAPIs Pricing page.

Billing is purely per call, with no monthly tier to commit to. Reads run $0.0008 a call and return roughly 20 tweets, which works out to $0.04 per 1,000 tweets; simple write actions run the same $0.0008 a call, and creating a tweet runs $0.0016. To project a real monthly figure for your workload, run the numbers through the Twitter API Cost Calculator or check the Twitter API Pricing Comparison.

Yes. Every new account starts with $0.50 in free credits, enough to make live calls right away, and we never ask for a card to begin testing.

For one-off scripts and quick experiments an unofficial Twitter API is fine, but anything you put in front of real users needs predictable uptime and a clear stance on platform policy. Weigh those tradeoffs in the Twitter unofficial API guide before you settle on a stack.

No. There are no X developer app credentials to apply for or maintain. Create an account, copy your key, and your first request can go out in minutes.

The Twitter API alternatives and X API alternatives page lays each option out side by side. Judge them on how they bill, how they treat rate limits, and how fast you can wire them into your code for the job you actually have.

No. There are no platform-imposed rate limits and no per-endpoint quotas; you can hit any route as fast as your remaining credits allow. The Twitter API Rate Limits Comparison shows how that differs from the throttling on the official X API.

The only personal details we keep are your email and name. Most routes are read-only against public data. For private reads and write actions such as like, retweet, bookmark, and follow, you either register an X session, which is stored encrypted at rest with AES-256-GCM until you replace it, or pass one per request, which is never stored. Everything moves over encrypted HTTPS, and your data is never sold or shared. The full breakdown is on our Privacy & Data Handling page.

Start fetching Twitter data today.

$0.50 free credits on signup. No credit card. No developer account. Just an API key and your first call running in under 5 minutes.

No credit card required · $0.0008 per call · Cancel anytime