Use the Ruby SDK for Ruby 3.2+ applications that need typed REST access, retries, Yard docs, RBS, RBI, and connection pooling. Use this page when you need a Ruby app, Rails job, or Sidekiq worker to search tweets, scrape tweets to CSV, JSON Lines, or XLSX, export followers, upload media, send direct messages, monitor tweets, or hand X data to a warehouse, CRM, queue, or agent workflow.Documentation Index
Fetch the complete documentation index at: https://docs.xquik.com/llms.txt
Use this file to discover all available pages before exploring further.
Install
Authenticate
Basic Example
Search tweets and write durable JSON Lines handoff rows:Workflow: Search Tweets to CSV, JSON Lines, or XLSX
This job is for Ruby workers, Rails jobs, Sidekiq queues, and agent tools that need tweet search results in durable handoff files. It callsGET /x/tweets/search through client.x.tweets.search, uses the generated XTwitterScraper::X::TweetSearchParams shape, and writes analyst-friendly CSV plus JSON Lines for queues, warehouses, and replayable processing.
q
Ruby keyword
q maps to REST q. Use it for the required X search query with keywords, handles, hashtags, or operators.limit
Ruby keyword
limit maps to REST limit. Use it for a bounded request from 1 to 200. Omit it for cursor loops.cursor
Ruby keyword
cursor maps to REST cursor. Pass the opaque cursor from page.next_cursor to request the next page.since_time
Ruby keyword
since_time maps to REST sinceTime. Use it as the ISO 8601 lower time bound.until_time
Ruby keyword
until_time maps to REST untilTime. Use it as the ISO 8601 upper time bound.query_type
Ruby keyword
query_type maps to REST queryType. Use :Latest for chronological results or :Top for engagement-ranked results.Returned Data & Handoff
client.x.tweets.search returns XTwitterScraper::PaginatedTweets:
page.tweets
JSON field
tweets. Contains SearchTweet records with id, text, optional author, created_at, like_count, reply_count, retweet_count, quote_count, bookmark_count, view_count, and is_note_tweet when available.page.has_next_page
Ruby field
page.has_next_page. JSON field has_next_page. Tells your worker whether another page exists.page.next_cursor
JSON field
next_cursor. Store it with the job checkpoint and pass it back as cursor.page.tweets into CSV rows for analysts and JSON Lines rows for queues and data lakes. Store tweet_id, author_username, engagement counts, page_index, page_cursor, next_cursor, and has_next_page in xquik-tweet-search.jsonl so workers can resume safely or load the same records into XLSX, CRM, warehouse, or agent workflows.
Workflow: Follower Export to CSV, JSON, or XLSX
Use this workflow when a Ruby app, Rails job, Sidekiq worker, or agent tool needs an owned follower list for a CRM import, warehouse load, analyst CSV file, XLSX workbook, or resumable JSON handoff. It callsPOST /extractions/estimate through client.extractions.estimate_cost, creates the job with client.extractions.run, reads saved rows with client.extractions.retrieve, and downloads files with client.extractions.export_results.
follower_explorer requires target_username. Persist job.id, target_username, estimate.estimated_results, and estimate.source before polling so a Sidekiq retry, Rails job retry, or worker restart can resume the same follower export. client.extractions.retrieve returns results, has_more, and next_cursor; pass next_cursor back as after when you need stored JSON pages before exporting files. Map exported User ID or row xUserId as the CRM unique key. Use xquik-followers.jsonl for queue replay or warehouse loads, xquik-followers.json for app ingestion, xquik-followers.csv for CRM import, and xquik-followers.xlsx for analyst handoff. Cost: 1 credit per follower extracted or returned. Exports are free after the extraction job exists.
Workflow: Tweet Replies to CSV, JSON, or XLSX
Use this workflow when a Ruby app, Rails job, Sidekiq worker, or agent tool needs every reply under one tweet as a saved extraction, JSON Lines handoff, or CSV/JSON/XLSX file export. It callsPOST /extractions/estimate through client.extractions.estimate_cost, creates the job with client.extractions.run, reads rows with client.extractions.retrieve, and downloads files with client.extractions.export_results.
reply_extractor requires target_tweet_id. client.extractions.retrieve returns results, has_more, and next_cursor; store those values when you need resumable JSON pagination. Use xquik-replies.jsonl for queue replay or warehouse loads, xquik-replies.json for app ingestion, xquik-replies.csv for CRM import, and xquik-replies.xlsx for analyst handoff. client.extractions.export_results supports :csv, :json, and :xlsx for file handoff. Cost: 1 credit per reply extracted or returned.
Workflow: Post Media Tweets and DM Attachments
Use this workflow when a Ruby app, Rails job, Sidekiq worker, or agent service needs to post a media-backed tweet, reply with media, or send one uploaded media item in a DM. Tweet and reply media posts use public media URLs directly onPOST /x/tweets. Send up to 4 image URLs or exactly 1 MP4 video URL up to 100 MB. Do not mix video with other media. Do not upload first when the media URL is already public.
Use client.request when a write worker must branch on the REST 202 x_write_unconfirmed response. The generated client.x.tweets.create helper is still useful when your flow only continues after a confirmed tweet.tweet_id.
reply_to_tweet_id:
media.media_id as the only media_ids item:
write_action_id and charged_credits, then poll Get Write Action Status before retrying a pending tweet or reply. client.x.tweets.create returns tweet.tweet_id for confirmed-only flows. client.x.media.upload returns media.media_id for DM attachments, and client.x.dm.send_ returns dm.message_id for support tickets, CRM records, queue jobs, or agent memory.
Text-only tweet and reply writes cost 10 credits. Tweet media adds 2 credits per started MB across attached files. Uploading media costs 10 credits, and sending the DM costs 10 credits. Do not pass uploaded media.media_id values to client.x.tweets.create; that method uses media with public media URLs.
Cost, Limits & Retries
Tweet search costs 1 credit per tweet returned. If remaining credits cannot cover a boundedlimit request, the API can return fewer tweets; if 0 paid results are affordable, it returns 402 insufficient_credits. Read calls are rate-limited, and 429 responses include Retry-After.
The client retries connection errors, timeouts, 408, 409, 429, and 5xx responses by default. Handle XTwitterScraper::Errors::RateLimitError with backoff, and fix 400, 401, 403, 404, or 422 responses before retrying.
Error Handling
All SDK errors inherit fromXTwitterScraper::Errors::APIError.
400 Bad Request
Throws
BadRequestError.401 Unauthenticated
Throws
AuthenticationError.403 Permission Denied
Throws
PermissionDeniedError.404 Not Found
Throws
NotFoundError.422 Unprocessable Entity
Throws
UnprocessableEntityError.429 Rate Limited
Throws
RateLimitError.5xx Server Error
Throws
InternalServerError.Pagination
Paginated responses expose fields such ashas_next_page. Pass the endpoint’s cursor fields when requesting more pages.