X (Twitter) Search & Discovery Scraper

Search public X posts with the official X API v2 and export clean, normalized records for research, monitoring, analytics, and downstream automation.

What this Actor does

• Searches public X posts using one or more short queries.
• Supports recent search and full-archive search when your X developer access allows it.
• Normalizes post text, author data, timestamps, engagement metrics, media, conversation IDs, and quote/reply relationships.
• Deduplicates overlapping results across queries while preserving query provenance.
• Applies optional language and engagement filters.
• Keeps strict caps on items, pages, retries, and runtime so costs are easier to control.
• Uses your own X Developer Bearer Token.

Bring your own X API token

Live X access uses a BYOT (bring your own token) model.

Enter your X Developer Bearer Token in the bearerToken field. The field is marked as a secret input, so Apify encrypts it before storing the run input.

Important:

• X API usage is billed by X to the developer account that issued the token.
• Store users never use a NexaScout X credential.
• The Actor does not fall back to an owner-level X token.
• Live requests are locked to the official X API host.
• The token is not written to the dataset or run summary.

Quick start

Use a small recent-search run first:

{
  "queries": [
    "\"manual process\" automation",
    "\"copy paste\" workflow"
  ],
  "bearerToken": "YOUR_X_BEARER_TOKEN",
  "searchMode": "recent",
  "maxItems": 25,
  "maxItemsPerQuery": 15,
  "maxPagesPerQuery": 1
}

Main inputs

queries

One or more X search queries. Short, focused queries usually produce cleaner research data than one very broad query.

Examples:

• "manual process" automation
• Shopify "spreadsheet" inventory
• CRM "manual data entry"
• "real estate" "takes hours"

bearerToken

Your X Developer Bearer Token. Required for live X collection.

searchMode

• recent — uses X recent search.
• all — requests full-archive search. Your X developer project must have access to that endpoint.

Cost-control inputs

Use maxItems, maxItemsPerQuery, maxPagesPerQuery, maxRetries, and maxRuntimeSec to keep runs bounded.

Output

Each dataset row represents one normalized public X post. Common fields include:

• postId
• url
• authorId, authorHandle, authorName
• text
• lang
• createdAt
• engagement metrics
• conversationId
• inReplyToId
• quote/retweet indicators
• matchedQueries
• searchQuery

The run also stores a RUN_SUMMARY record with query-level counts, retries, rate-limit hits, warnings, and totals.

Good use cases

• Brand and product mention monitoring
• Competitive research
• Market and category research
• Customer pain-point discovery
• Lead-signal discovery
• Trend and conversation discovery
• Building a normalized X data layer for agents or automations

Pricing

Apify Store charges for the Actor are separate from X API charges.

Your X Developer account is responsible for X API usage generated by your token. Check current X API pricing and limits in your X Developer Console before large runs.

Limitations

• Only data returned by the official X API is available.
• Protected, unavailable, deleted, or otherwise inaccessible posts are not returned.
• Full-archive search depends on the capabilities of your X developer project.
• X rate limits and product limits still apply.
• This Actor does not automate login, posting, liking, following, or other engagement actions.

This Actor is not affiliated with X Corp.