Skip to main content
Search tweets, API keys, signed webhooks, and user profiles appear in this changelog. So do REST, MCP, authentication, billing, and writes.
v1
Changed
  • The price lists now show the X sign-in fee. A write that must sign in to your X account first adds 10 credits. Xquik refunds them if the sign-in fails. See X sign-in fee
  • A past time over 24 hours from every stored list now answers 404 not_found. It answered 400 invalid_input. So does a GET /x/trends/history range that ends before a place’s first stored list. Both cost nothing. An unknown place name & unreadable input still answer 400
  • Connect links let your users connect an X account on a page Xquik hosts. They need no Xquik signup. Your backend never receives their password. See Connect your users’ X accounts
  • Connect links now need Connect X accounts on the API key. That covers making, listing, reading & revoking them. A link stops while its key is paused or lacks that permission. It ends once that key is revoked, rotated, expired or deleted. Each link names that key in apiKeyId. GET /x/account-connection-links lists your links. A sign-in with missing details answers 400 & leaves the link as it was
  • A new key permission, Connect X accounts, opens this API to your backend. It connects, reconnects, retries & disconnects X accounts. It starts off, and Full access doesn’t include it. Only a dashboard session can turn it on. See Connect your users’ X accounts. MCP tools still never take X passwords
  • X account logins no longer stop at 10 per 15 minutes. Failed logins slow a caller down, & each account it connects lifts that limit. Reconnects follow the same limits & cooldowns
  • POST /x/accounts/{id}/reauth can answer 202 for an email code, & 409 x_account_mismatch for another X account’s sign-in
  • POST /x/media/download takes any number of posts in tweetIds, where it took 50. Posts it had no time to read come back in unprocessedTweetIds at no charge. Send them again
  • GET /x/tweets & GET /x/users/batch take as many IDs as fit in 1 URL. They took 100
  • GET /x/users/batch/tweets takes any number of users, where it took 20. pageSize goes up to 300 posts a user. Users it had no time to read come back in unprocessed_ids at no charge
  • GET /x/users/{id}/insights & GET /x/users/{id}/shadowban read past where X ends a profile timeline. So limit=2000 returns 2,000 posts. The rows below that place come from search, which can miss a few posts
  • sample.read in user insights gives the posts read. sample.posts gives the posts the averages used
  • Every Community route takes an ID or a URL-encoded x.com/i/communities link. So does the communityId search filter
  • Changes to Xquik resources get 6,000 requests per minute, DELETE included. X (Twitter) actions through a connected account keep 120 per minute. A 429 message names the limit and the wait
  • Extraction jobs take up to 10,000 items per target list. That covers usernames, search queries, Community IDs, List IDs & profile relations
  • POST /x/communities answers 422 x_community_creation_closed and charges nothing. X stopped accepting new Communities in April 2026
  • An empty last page from GET /x/users/{id}/tweets, GET /x/users/{id}/replies or GET /x/tweets/search can carry hiddenTimeline. It means X shows that account’s timeline to nobody
  • An MCP answer over 24,000 characters now stays valid JSON. It keeps whole items from the start. Each cut says --- TRUNCATED ---. truncated holds the full size, next, result_id & a CSV download_url
  • The execute tool states what 1,000 credits cost in dollars
  • The execute tool says its 55 seconds include waits. It also says how long a post can take. A script past the limit with no request running gets a refusal. The refusal names its last successful request
  • Hidden likers answer 424 favoriters_unavailable. The message names the post’s retweeters path
New
  • GET /x/tweets/search takes topic & keeps only posts about it, such as the Rust programming language. Each kept post carries its topicScore, & topicFilter states the 0.5 cutoff. Each kept post costs 2 credits. MCP’s searchTweets takes it too
  • POST /x/users/{id}/block blocks a user from a connected X account, & DELETE unblocks. POST /x/users/{id}/mute mutes, & DELETE unmutes. Each call costs 10 credits
  • POST /x/tweets/{id}/bookmark bookmarks a post from a connected X account, & DELETE removes the bookmark. Each call costs 10 credits like other writes, & MCP clients get both through execute
  • POST /x/media/download takes imageShows & saves only posts whose photos show it. Each saved post costs 2 credits, on top of the save price
  • POST /extractions takes topic or imageShows on tools that return posts. It stores only the posts that match. Each stored post costs 2 credits instead of its read price. A dropped post costs nothing. The job’s topicFilter or imageFilter states the cutoff & counts
  • GET /x/users/{id}/tweets, /replies & /media take imageShows & keep only posts whose photos show it. Send charts, screenshots, product_photos, memes, people or your own words. They take topic too, & search takes imageShows. Each kept post costs 2 credits
  • AI analysis now reads each post’s images with its text, at no extra cost
  • Send analysis.images: false to analyze the text alone. Images of posts X marks sensitive stay unread
  • contextAvailability.media is images when the AI read a post’s images. An image-only post now gets answers
  • GET /x/users/{id}/shadowban checks 1 X account. It looks for a search ban, a search suggestion ban & reply deboosting. It also says if the account is active, protected or suspended
  • Each check answers pass, fail or unknown with its reason. It also names the posts, suggestions or replies it read. It costs 1 credit per profile, post, suggestion & reply in the answer. Guest keys can call it
  • Sentiment analysis adds emotion, the main emotion of each post, at the same price. It answers joy, anger, sadness, fear, surprise, disgust or none
  • GET /radar search trend items add volumes. It lists each search volume change with its time
  • Each search trend news story adds its imageUrl & publishedAt when the story has them
v1
v1
v1
v1
v1
v1