What this API is and who it is for
This is an unofficial, third-party scraper API that exposes Twitter/X data through a conventional REST interface hosted at scraper.tech. Because it is built on scraping rather than Twitter's own developer platform, it sidesteps the restrictions and approval process of the official API — a meaningful practical difference for developers who need access to data that the official tiers either price prohibitively or restrict outright.
The primary audience is developers building social media analytics dashboards, influencer monitoring tools, brand-sentiment trackers, content aggregators, or research pipelines. It is also relevant to anyone building automation that needs to read Twitter data without maintaining their own scraping infrastructure.
Being unofficial carries inherent risks that any developer should evaluate before committing: Twitter's internal structure can change at any time, the provider may not always keep pace immediately, and there are no formal SLA guarantees of the sort an official platform would offer. That said, the marketplace-reported average success rate of 100% and 18,519 subscribers suggest the service has been reliably maintained.
Endpoint coverage
The API exposes 30 GET endpoints. All requests use query parameters rather than request bodies, consistent with a scraper-style backend. Here is a breakdown by functional area:
User and account data
/screenname.php— full profile metadata for a given screen name (bio, location, profile details)/about.php— account registration details and usage information/screennames.php— batch-fetch profiles by internal Twitter rest_id values/affilates.php— affiliate/associated accounts for corporate profiles/broadcast.php— check whether a user is currently live-streaming
Timeline and content
/timeline.php— latest tweets from a user's timeline/usermedia.php— images, videos, and GIFs posted by a user/replies.php— replies posted by a user/latest_replies.php— latest replies to a specific tweet/tweet_thread.php— full conversation thread starting from a tweet/tweet.php— detailed metadata for a single tweet (likes, retweets, content)
Social graph
/following.phpand/followers.php— following and follower lists/checkfollow.php— determine if user A follows user B (note: documented as unreliable for large accounts or old relationships)/retweets.php— list of users who retweeted a tweet/checkretweet.php— check if a specific user retweeted a tweet (documented as potentially inaccurate for older retweets)
Discovery and search
/search.php— keyword and hashtag search; rate-limited to 60 requests/minute for new customers; higher limits available on request/trends.php— trending topics by country (contact the provider to request additional countries)/jobs.php— job listings from x.com/jobs
Communities and Lists
/community_timeline.php,/community_members.php,/community_info.php— community posts, member lists, and metadata/search_communities.php,/search_communities_top.php,/search_communities_latest.php— community discovery and post search/listtimeline.php,/list_members.php,/list_followers.php— Twitter List content and membership
Spaces
/spaces.php— basic metadata for Twitter Spaces (live audio rooms)
Misc
/top_posts.php— posts from Twitter's creator inspiration feed
All endpoints are GET-only. The design is simple: supply identifiers (screen names, tweet IDs, rest_ids) as query parameters and receive JSON responses.
Pricing
| Plan | Price | Requests/month | Overage per request |
|---|---|---|---|
| BASIC | $0 | 1,000 | — |
| PRO | $9 | 100,000 | $0.0001 |
| ULTRA (recommended) | $99 | 2,000,000 | $0.0001 |
| MEGA | $490 | 10,000,000 | $0.0001 |
The free BASIC tier gives you 1,000 requests per month — enough to prototype and validate that the endpoints return the data shape your application needs, but not enough for any sustained workload. At that quota you can fetch roughly 33 user profiles per day, or use a mix of endpoint calls for light testing.
The PRO plan at $9/month is the entry point for real usage. 100,000 monthly requests works out to roughly 3,300 calls per day, which is workable for small monitoring tools or lightweight analytics. Overage charges of $0.0001 per additional request apply, so a 20% overrun on PRO costs about $2 extra.
ULTRA at $99/month (the provider-recommended tier) provides 2 million requests — approximately 66,000 per day — which suits mid-scale analytics pipelines, dashboards serving multiple clients, or applications that poll timelines frequently. At $0.0001 overage, even significant spikes remain inexpensive.
MEGA at $490/month covers 10 million requests per month (roughly 333,000/day) and is aimed at high-volume data consumers or resellers.
Performance characteristics
The marketplace-reported average latency is 1,753 ms. This is typical of scraper-based APIs — each call may need to fetch and parse a live page or internal API response rather than hitting a low-latency database. Budget for this in your application: calls should be made asynchronously, results should be cached where possible, and any user-facing features should not wait on synchronous responses.
The reported average success rate is 100%, which reflects the aggregate across all logged requests in the marketplace data.
Practical use cases
- Competitor and brand monitoring: poll
/search.phpon brand keywords and/timeline.phpfor competitor accounts on a schedule. - Influencer analytics: combine
/screenname.php,/usermedia.php,/followers.php, and/tweet.phpto build engagement dashboards. - Trend research: use
/trends.phpand/search.phptogether to surface and contextualise rising topics. - Community intelligence: the community endpoints (
/community_timeline.php,/community_members.php,/search_communities.php) cover data that is difficult to obtain via the official API. - Verification tooling:
/checkfollow.phpand/checkretweet.phpcan power giveaway or engagement-verification workflows, though both carry documented accuracy caveats.
Limitations and things to verify before integrating
Unofficial status: Because this is a scraper, changes to Twitter/X's internal structure — a routine occurrence — can break endpoints without warning. Build your integration with graceful error handling and monitor endpoint health.
Accuracy caveats: The provider explicitly flags /checkretweet.php as potentially unsuitable for old retweets, and /checkfollow.php as potentially unreliable for large accounts or old subscriptions. Treat these as best-effort rather than authoritative.
Search rate limit: The /search.php endpoint is capped at 60 requests/minute for new accounts. If your use case is search-heavy, contact the provider before building around the assumption you can exceed this.
Latency: At ~1.75 seconds average, this API is not suited for real-time, latency-sensitive user interactions. It works well in background jobs, scheduled tasks, and asynchronous pipelines.
Terms of service: Using a scraper to access Twitter/X data may conflict with Twitter's terms of service. Assess your legal and compliance posture accordingly.
Getting started
The API is available through the RapidAPI marketplace, where you can subscribe to the BASIC tier for free and begin making requests immediately. Additional documentation is published at scraper.tech/en/docs/. For questions about rate limits, custom plans, or missing country support in /trends.php, the provider can be reached at [email protected] or via Telegram at @AlexanderVikhorev.
