CHANGELOG
Changelog
TwitterAPIs is a pay-per-call Twitter/X data API that ships frequent updates. This Changelog is a chronological record of every new endpoint, pricing change, infrastructure update, and product launch since the February 2026 public release. Each entry names the exact route, the parameters that changed, and the per-call price, so you can act on it without opening the docs.
How we price these releases
Written by Emma, twitterapis developer relations
Standard reads are a flat $0.0008 per call, about 20 tweets each, and the June 2026 price consolidation below left them untouched. Premium endpoints run $0.0016 to $0.004. There is no subscription and no monthly minimum, so an endpoint's price is the whole cost of calling it.
Endpoint rates re-checked August 2, 2026 against the biller's own price table, not against another page.
August 2, 2026
Blocking and muting lists are live
Read the accounts your own authenticated account has blocked or muted, returned as full user objects with cursor pagination. Both are standard reads at $0.0008 per call.
- -GET /twitter/user/blocking, the accounts you have blocked
- -GET /twitter/user/muting, the accounts you have muted. Muting hides someone's posts without blocking them, so the two lists differ and an account can sit on one and not the other
- -These read your own lists only. X offers no way to read another account's block or mute list, so there is no user_id parameter
- -An empty users array means you block or mute nobody. A list we cannot read comes back as an error status instead, so an empty page is never a silent failure
- -$0.0008 per call, cursor paginated
August 2, 2026
User About returns protected status and affiliate label
GET /twitter/user/user_about now tells you whether an account is protected, and returns the affiliate label X shows on accounts tied to a verified organization. Price is unchanged at $0.0008 per call.
- -protected, true when the account's posts are visible to approved followers only
- -affiliate_label, the parent organization X displays on an affiliated account
- -Both fields were confirmed against a live capture before shipping, not inferred from the old response shape
- -Purely additive. Existing parsers keep working untouched
August 2, 2026
MCP server 0.6.3 covers all 51 endpoints
The @twitterapis/mcp Model Context Protocol server now exposes every endpoint as a native tool, including trends, batch user lookup, media readiness, and the new blocking and muting lists. The tool catalog is generated from the published API spec at build time, so a new endpoint can no longer be forgotten by hand.
- -Install: npx -y @twitterapis/mcp@latest
- -51 tools, one per endpoint, generated from the same OpenAPI spec the REST API publishes
- -Hand-written tool descriptions are kept where they explain a real gotcha, for example that media uploads process asynchronously
- -Registry descriptors ship with the package, so MCP client directories can list it
- -Every call bills at the same rate as the REST endpoint behind it
August 2, 2026
Twelve new pages: free tools, SDK guides, status, integrations
Four browser tools that need no API key, SDK quickstarts for Node, Python and Go, a public status page, an integrations directory, and an about page.
- -/tools, carrying Twitter ID Finder, Tweet Counter, Follow Checker and an Engagement Calculator. No signup and no key needed
- -/sdk with /sdk/node, /sdk/python and /sdk/go, copy-paste clients per language
- -/status, endpoint health in one place
- -/integrations, what TwitterAPIs plugs into
- -/about, who runs this and how it is operated
August 2, 2026
Stored credentials are encrypted at rest
Every credential we store is now encrypted with AES-256-GCM before it reaches the database. That includes the auth_token and ct0 of the customer sessions you register with us, not just the accounts behind our own read pool.
- -AES-256-GCM authenticated encryption, so a tampered ciphertext fails to decrypt instead of returning altered data
- -Covers customer_sessions auth_token and ct0, the credentials you hand us when you register a session
- -Covers the credentials of the pooled accounts that serve shared reads
- -No API change and nothing to update in your integration
July 31, 2026
Batch user lookup is live
Resolve up to 100 numeric user IDs into full profiles in a single call instead of looping the single-user endpoint. The common case is hydrating the authors of a batch of tweets.
- -GET /twitter/users/by_ids, up to 100 ids per call
- -Returns the same user object as /twitter/user/info_by_id, as a list
- -IDs that no longer resolve, from suspended or deleted accounts, are omitted rather than returned as nulls. Diff the ids you sent against the ids you got back to see which were dropped
- -Sending more than 100 ids is rejected rather than silently truncated
- -Bills per resolved user at the standard $0.0008 rate
July 24, 2026
Media processing status is live
Check whether an uploaded media_id has finished processing on X before you attach it to a tweet. Video, GIF and large uploads process asynchronously, so an upload that already returned a media_id is not necessarily ready to post.
- -GET /twitter/media/status?media_id=<id>
- -Returns state as pending, in_progress, succeeded or failed, plus progress_percent
- -check_after_secs carries how long X wants you to wait before polling again. Honour it rather than tight-looping
- -An error object comes back when state is failed, so a rejected upload is visible instead of silent
- -$0.0008 per call
July 21, 2026
User About returns account origin fields
GET /twitter/user/user_about now reports where an account is based, what it signed up through, and how many times it has changed handle. These are the fields most people want for account-age and authenticity checks. No price change.
- -account_based_in, the country X attributes the account to
- -created_via, the client the account was created through
- -username_changes, how many times the handle has changed
- -Purely additive. Existing parsers keep working untouched
July 20, 2026
Trends API is live
Fetch the current top X trends for any country or city, with a companion endpoint that lists every location trends can be served for. $0.0008 per call, the same as any standard read.
- -GET /twitter/trends, top trends for a location. With no location it returns Worldwide
- -Pass country as an ISO code or a country name, for example US or Japan, or pass a numeric woeid. woeid wins when you send both
- -GET /twitter/trends/locations, every location trends are available for, with its woeid
- -The response carries the resolved location and the as_of timestamp, so you always know what was measured and when
- -A location X will not serve returns a 400 rather than a misleading empty list
July 20, 2026
Account and login endpoints on the main API host
The free account endpoints are now served from the same host as the rest of the API, and the login endpoint answers on a shorter path. One base URL for everything.
- -GET /account/me and GET /account/payments answer on the public API host. Still free, still 30 requests per minute
- -POST /twitter/user_login now works as an alias for /twitter/user/user_login. Both paths are served, so nothing you have already written breaks
July 5, 2026
Write, DM and session endpoints are documented
The half of the API that was live but undocumented now has reference pages and is carried in the OpenAPI spec: posting and deleting tweets, direct messages, and the reads that run on your own session.
- -tweet/create and tweet/delete
- -dm/list, dm/conversation and dm/send
- -home_timeline, bookmarks, bookmark_search, likes and followers_you_know
- -media/upload, plus user/tweets/complete
- -Copy-paste examples corrected to the live contract, including the /twitter/ path prefix and the id parameter
- -public/openapi.json is generated from the same source the docs read, so the spec and the reference pages cannot drift apart
June 29, 2026
One canonical price table, simple writes cut to the read rate
Every endpoint moved onto a single price table. Simple write actions dropped to the standard read rate, and the two endpoints that expand a whole thread or a whole timeline moved up to reflect the work they do.
- -Like, unlike, retweet, unretweet, bookmark, unbookmark, follow, unfollow, delete tweet and media upload: $0.0015 down to $0.0008, the standard read rate
- -Direct messages, tweet creation and profile updates: $0.0015 up to $0.0016
- -GET /twitter/tweet/thread: $0.0008 up to $0.004, because it resolves a tweet to its root and walks the entire self-thread
- -GET /twitter/user/tweets/complete: $0.0008 up to $0.0024, because it expands self-threads across a whole page of results
- -Standard reads were not touched and stayed at $0.0008
June 11, 2026
User Tweets Complete endpoint is live
Fetch a user's recent tweets-and-replies timeline with self-thread expansion, so thread continuations inside the recent window come back more completely than the standard /user/tweets page. $0.0024 per call, 40 raw items per page before expansion.
- -GET /twitter/user/tweets/complete?userName=<handle>&cursor=<optional>
- -Expands detected self-threads (capped at 20 roots per page; `complete` flags when the cap is exceeded)
- -$0.0024 per call (vs $0.0008 for the standard /user/tweets page), priced for the extra thread-expansion work
- -Expanded threads can overlap adjacent pages, dedupe by tweet `id` when paginating with next_cursor
June 11, 2026
Tweet Thread endpoint is live
Resolve a full linear self-thread from any tweet in it, pass any tweet ID and get the ordered thread back, walking only the original author's linked replies. $0.004 per call.
- -GET /twitter/tweet/thread?id=<tweetId>
- -Works from any tweet in the thread, resolves to the root, then walks the author's self-replies in order
- -No auth_token parameter required. Uses shared read access.
- -Response flags when a very long thread is truncated at the pagination cap
June 10, 2026
Tweet Retweeters endpoint is live
Fetch the full list of users who reposted (retweeted) any tweet. $0.0008 per call, ~20 users per page with cursor pagination. Closes the competitor gap with twitterapi.io's get_tweet_retweeter.
- -GET /twitter/tweet/retweeters?id=<tweetId>&cursor=<optional>
- -No auth_token parameter required. Uses shared read access.
- -Returns tweetId, user_count, has_more, next_cursor, and a users array with full profile data (followers, verified status, bio, location, etc.)
- -Paginate by passing next_cursor until has_more is false
May 31, 2026
Twitter / X MCP Server now available on npm
The official @twitterapis/mcp Model Context Protocol server is now published on npm and open-sourced on GitHub. Plug the Twitter/X read API into Claude Desktop, Cursor, Cline, or any MCP-compatible client with a one-line install. Calls bill at the standard TwitterAPIs rate of $0.0008 per read.
- -Install: npx -y @twitterapis/mcp@latest
- -Drop a small config block into claude_desktop_config.json or the Cursor MCP settings panel, restart the client, and the tools appear
- -Read tools map onto TwitterAPIs read endpoints: tweet/advanced_search, tweet/detail, tweet/replies, tweet/thread, user/info, user/tweets, user/mentions, user/followers, and more
- -Open-sourced on GitHub at github.com/TwitterAPIs/twitterapis-mcp
- -Full value prop, code samples, and FAQ at /mcp
May 6, 2026
Referral program is live
Earn 20% lifetime commission on every payment from anyone you refer. Open to every TwitterAPIs user, your unique referral link is generated automatically.
- -20% of gross on every payment from referred customers, lifetime
- -$5,000 / calendar year cap per affiliate
- -30-day pending holdback before commission becomes available
- -Convert available earnings to API credits with a +15% bonus
- -Find your link and balance at /dashboard/referrals
April 1, 2026
Account Info & Payment History endpoints
Two new free endpoints to check your TwitterAPIs account details and payment history. No credits deducted, rate limited to 30 requests per minute.
- -GET /account/me, credit balance, usage summary, account details
- -GET /account/payments, payment/top-up history
- -Free to use, no credits consumed
- -Rate limited: 30 requests/min per API key
March 31, 2026
User Affiliates endpoint is live
Get affiliated accounts of verified organizations (companies, brands, nonprofits). Returns ~20 users per page with cursor pagination. $0.0008 per call (~20 tweets).
- -GET /twitter/user/affiliates
- -Returns affiliated accounts of verified organizations
- -Cursor-based pagination (~20 users per page)
- -Includes full profile data for each affiliate
March 16, 2026
Search Users endpoint is live
Search for Twitter/X users by keyword, username, or topic. Equivalent to the "People" tab in Twitter search. $0.0008 per call (~20 tweets).
- -GET /twitter/user/search
- -Search by keyword, username, or topic
- -Returns up to 20 users per page with full profile data
- -Cursor-based pagination support
March 14, 2026
Blog is live
TwitterAPIs now has a blog. Read guides, tutorials, and comparisons to get the most out of the Twitter API.
- -SEO-optimized blog pages with structured data
- -Syntax-highlighted code snippets with copy button
February 22, 2026
Followers v2 & Following v2 endpoints
Two new endpoints. $0.0008 per call (~50 tweets).
- -GET /twitter/user/followers_v2
- -GET /twitter/user/following_v2
February 11, 2026
Payment integration is live
You can now purchase API credits directly from the dashboard via Stripe. Two credit packs are available, $10 and $50. No subscriptions, no recurring charges. Credits are added instantly and never expire.
- -Secure one-time payments powered by Stripe
- -$10 Starter pack (~10,000 API calls) and $50 Pro pack (~50,000 API calls)
- -Credits added to your account instantly after payment
- -Payment history visible in your dashboard under Credit History
February 9, 2026
TwitterAPIs public launch
TwitterAPIs launched publicly with the cheapest pay-as-you-go Twitter/X API pricing on the market. $0.0008 per call (~20 tweets) for every endpoint, and $0.50 in free credits for every new account.
- -21 API endpoints covering tweets, users, search, and lists
- -Pay-per-call pricing with no subscriptions or monthly fees
- -99.9% uptime SLA with sub-2-second response times
- -Full API documentation at docs.twitterapis.com
Next read
Continue exploring TwitterAPIs:
TwitterAPIs pricing
Endpoint-level costs and per-call totals.
Twitter API pricing comparison
Monthly economics and request-level cost side by side.
Twitter scraper API
Scrape tweets, profiles, and followers at $0.04 per 1,000.
TwitterAPIs MCP server
Wire the full Twitter API into Claude, Cursor, and Cline.